Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-2585: Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a me

51
This month
MEDIUM 5.9REMOTEWATCHLISTUPGRADEDOWNGRADE

CVE-2017-2585 is a medium-severity flaw (CVSS 5.9) affecting keycloak, single sign on. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance2.0% (top 20%)
CISA exploited listNo
WeaknessCWE-200
Published2018-03-12
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

redhat keycloak UPGRADE
Affected: < 2.5.1
Fixed in: 2.5.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy keycloak || rpm -q keycloak || keycloak --version
2. UPGRADE to 2.5.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade keycloak
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade keycloak
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat single sign on DOWNGRADE
Affected: 7.1 · 7.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.1
1. Check installed version
apt-cache policy single-sign-on || rpm -q single-sign-on || single-sign-on --version
2. No fixed release: DOWNGRADE to a release before 7.1 (Debian / Ubuntu)
apt-cache madison single-sign-on sudo apt install single-sign-on=<VERSION_BEFORE_7.1> sudo apt-mark hold single-sign-on
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list single-sign-on sudo dnf downgrade single-sign-on-<VERSION_BEFORE_7.1> sudo dnf versionlock add single-sign-on
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-2585?

keycloak: upgrade to 2.5.1; single sign on: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-2585 being exploited?

CVE-2017-2585 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-2585 affect?

CVE-2017-2585 affects keycloak, single sign on. Severity is medium (CVSS 5.9). 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.

How urgent is CVE-2017-2585?

Priority 51/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

Keycloak vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.