GHSA-w6gv-3r3v-gwgj CVE-2017-2585
keycloak-core vulnerable to timing attacks against JWS token verification
- Severity
- 5.9 / 10
- Medium · CVSS 3.0
- Exploit chance (EPSS)
- 1.97%
- Chance of exploitation in the next 30 days. Higher than 80.47% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
2.5.1- Upgrade org.keycloak:keycloak-core to this version or later
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.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.keycloak:keycloak-core | < 2.5.1 |
2.5.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.keycloak:keycloak-core Maven → 2.5.1
- maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-core</artifactId><version>2.5.1</version></dependency>- gradle
implementation("org.keycloak:keycloak-core:2.5.1")
Severity breakdown
CVSS 3.0 5.9
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Other links
- access.redhat.com/errata/RHSA-2017:0872
- access.redhat.com/errata/RHSA-2017:0873
- bugzilla.redhat.com/show_bug.cgi
- web.archive.org/web/20170420113802/http://www.securitytracker.com/id/1038180
- web.archive.org/web/20200227175650/http://www.securityfocus.com/bid/97393
- rhn.redhat.com/errata/RHSA-2017-0876.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-q4xq-445g-g6ch Keycloak allows cross-site scripting (XSS) | Low | Also affects org.keycloak:keycloak-core |
| GHSA-93ww-43rr-79v3 Keycloak mTLS Authentication Bypass via Reverse Proxy TLS Termination | High | Also affects org.keycloak:keycloak-core |
| GHSA-w97f-w3hq-36g2 Keycloak Denial of Service vulnerability | High | Also affects org.keycloak:keycloak-core |
| GHSA-xmmm-jw76-q7vg Keycloaks's One Time Passcode (OTP) is valid longer than expiration timeSeverity | Medium | Also affects org.keycloak:keycloak-core |
| GHSA-g4gc-rh26-m3p5 Keycloak Open Redirect vulnerability | Medium | Also affects org.keycloak:keycloak-core |
| GHSA-9vm7-v8wj-3fqw keycloak-core: open redirect via "form_post.jwt" JARM response mode | Medium | Also affects org.keycloak:keycloak-core |
| GHSA-5q66-v53q-pm35 Keycloak vulnerable to Plaintext Storage of User Password | High | Also affects org.keycloak:keycloak-core |
| GHSA-5cc8-pgp5-7mpm Keycloak Untrusted Certificate Validation vulnerability | Medium | Also affects org.keycloak:keycloak-core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor