GHSA-f5h4-wmp5-xhg6 CVE-2023-2585
Client Spoofing within the Keycloak Device Authorisation Grant
- Severity
- 3.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.69%
- Chance of exploitation in the next 30 days. Higher than 52.95% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-358 Improperly Implemented Security Check for Standard
- Fix
- Available
- 2 packages have a fixed version
Description
Under certain pre-conditions the vulnerability allows an attacker to spoof parts of the device flow and use a device_code to retrieve an access token for other OAuth clients.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.keycloak:keycloak-server-spi-private | < 21.1.2 |
21.1.2 |
| org.keycloak:keycloak-services | < 21.1.2 |
21.1.2 |
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-server-spi-private Maven → 21.1.2
- maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-server-spi-private</artifactId><version>21.1.2</version></dependency>- gradle
implementation("org.keycloak:keycloak-server-spi-private:21.1.2")
org.keycloak:keycloak-services Maven → 21.1.2
- maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-services</artifactId><version>21.1.2</version></dependency>- gradle
implementation("org.keycloak:keycloak-services:21.1.2")
Severity breakdown
CVSS 3.1 3.5
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-358: Improperly Implemented Security Check for Standard
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
References
Advisories
Packages
Other links
- github.com/keycloak/keycloak/security/advisories/GHSA-f5h4-wmp5-xhg6
- github.com/keycloak/keycloak/commit/04e6244c387a1bde86184635a0049537611e3915
- access.redhat.com/errata/RHSA-2023:3883
- access.redhat.com/errata/RHSA-2023:3884
- access.redhat.com/errata/RHSA-2023:3885
- access.redhat.com/errata/RHSA-2023:3888
- access.redhat.com/errata/RHSA-2023:3892
- access.redhat.com/security/cve/CVE-2023-2585
- bugzilla.redhat.com/show_bug.cgi
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-v3f7-2p4r-mwfw Keycloak vulnerable to cross-site scripting (xss) via case-insensitive uri validation bypass | High | Also affects org.keycloak:keycloak-services |
| GHSA-9jrw-8xf7-xqhq Keycloak vulnerable to information disclosure through arbitrary filesystem path probing | Medium | Also affects org.keycloak:keycloak-services |
| GHSA-w3p3-7cjg-vgfw Keycloak allows unauthorized access to resources via uma permission ticket bypass | Medium | Also affects org.keycloak:keycloak-services |
| GHSA-f5p5-6xmx-p252 Keycloak vulnerable to authorization bypass via incorrect uri comparison | High | Also affects org.keycloak:keycloak-services |
| GHSA-r7rc-c989-86g6 Keycloak: Attacker can re-enable and take over disabled clients via registration access token | Medium | Also affects org.keycloak:keycloak-services |
| GHSA-4gv3-mc9p-5wqc Keycloak: Unauthenticated account takeover via reset-credentials flow bypass | Critical | Also affects org.keycloak:keycloak-services |
| GHSA-6g26-7cx5-mrrg Keycloak: Information disclosure due to user profile permission bypass | Low | Also affects org.keycloak:keycloak-services |
| GHSA-cpf7-j4cf-vqx4 Keycloak has an Out-of-bounds Read | Medium | Also affects org.keycloak:keycloak-services |
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