Skip to content
Fencer Vulns
medium 5.9

CVE-2017-2585 json

keycloak-core vulnerable to timing attacks against JWS token verification

published 2018-03-12 8 y ago modified 2026-06-17 4 mo ago also GHSA-w6gv-3r3v-gwgj , EUVD-2018-0707

cvss
5.9
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.

Patch / fix

  • maven org.keycloak:keycloak-core 2.5.1
  • redhat keycloak 2.5.1
  • rh-sso7 red hat single sign on 7 1-2.jbcs.el6
  • rh-sso7-zxing red hat single sign on 7 3.2.1-1.redhat_4.1.jbcs.el6
  • rh-sso7-runtime red hat single sign on 7 1-2.jbcs.el6
  • rh-sso7-keycloak red hat single sign on 7 2.5.5-2.Final_redhat_1.1.jbcs.el6
  • rh-sso7-liquibase red hat single sign on 7 3.4.1-2.redhat_2.1.jbcs.el6
  • rh-sso7-twitter4j red hat single sign on 7 4.0.4-1.redhat_3.1.jbcs.el6
  • rh-sso7-freemarker red hat single sign on 7 2.3.23-1.redhat_2.2.jbcs.el6
  • rh-sso7-zxing-core red hat single sign on 7 3.2.1-1.redhat_4.1.jbcs.el6

red hat advisories RHSA-2017:0872RHSA-2017:0873

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2585 updated cvss 3.7

keycloak: timing attack in JWS signature verification

  • Red Hat Mobile Application Platform 4 keycloak
    affected: no fix planned “Will not fix”
  • Red Hat Single Sign-On 7.1
    fixed: vendor fix RHSA-2017:0876
  • Red Hat Single Sign-On 7.1 for RHEL 6 Server rh-sso7 1-2.jbcs.el6, rh-sso7-runtime 1-2.jbcs.el6, rh-sso7-zxing 3.2.1-1.redhat_4.1.jbcs.el6, rh-sso7-libunix-dbus-java 0.8.0-2.jbcs.el6, rh-sso7-liquibase 3.4.1-2.redhat_2.1.jbcs.el6, rh-sso7-twitter4j 4.0.4-1.redhat_3.1.jbcs.el6, +9 more
    fixed: vendor fix RHSA-2017:0872
  • Red Hat Single Sign-On 7.1 for RHEL 7 Server rh-sso7 1-2.jbcs.el7, rh-sso7-runtime 1-2.jbcs.el7, rh-sso7-zxing 3.2.1-1.redhat_4.1.jbcs.el7, rh-sso7-libunix-dbus-java 0.8.0-2.jbcs.el7, rh-sso7-liquibase 3.4.1-2.redhat_2.1.jbcs.el7, rh-sso7-twitter4j 4.0.4-1.redhat_3.1.jbcs.el7, +9 more
    fixed: vendor fix RHSA-2017:0873

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-core
<2.5.1
2.5.1

Affected products

  • Red Hat, Inc. keycloak

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.