CVE-2017-2585 keycloak-core vulnerable to timing attacks against JWS token verification
Attackers can exploit non-constant time HMAC verification in Keycloak to perform timing attacks, potentially compromising token integrity and security.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-2585?
CVE-2017-2585 is a medium-severity vulnerability in Redhat Keycloak, published on 12 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2017-2585?
2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
org.keycloak:keycloak-core Maven | All versions | 2.5.1 |
org.keycloak:keycloak-core Maven | All versions | 2.5.1 |
Products include Redhat Keycloak, Redhat Single Sign On.
How do I fix CVE-2017-2585?
Upgrade org.keycloak:keycloak-core to 2.5.1 or later.
Is CVE-2017-2585 being exploited?
There is no known exploitation of CVE-2017-2585 in the wild and no public exploit code.
Other vulnerabilities in Redhat Keycloak
- CVE-2022-4361 Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC
- CVE-2022-1245 Keycloak vulnerable to privilege escalation on Token Exchange feature
- CVE-2021-20195 keycloak Self Stored Cross-site Scripting vulnerability
- CVE-2019-14910 Keycloak Authentication Error
- CVE-2019-14909 Keycloak Authentication Error
Sources
Also known as GHSA-w6gv-3r3v-gwgj.