dbcve.org
Single Sign OnApplication · Redhat

CVE-2023-2585

HIGH · 8.1 CVSS v3.1 Published 2023-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Keycloak's device authorization grant does not correctly validate the device code and client ID. An attacker client could abuse the missing validation to spoof a client consent request and trick an authorization admin into granting consent to a malicious OAuth client or possible unauthorized access to an existing OAuth client.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Keycloak's device authorization grant implementation fails to properly validate the device code and client ID during the OAuth device flow. This validation gap allows an attacker to craft malicious authorization requests that spoof legitimate client consent prompts, potentially tricking administrators into granting access to attacker-controlled OAuth clients or gaining unauthorized access to existing legitimate clients.

MitigationApply the vendor-provided security patch or upgrade Keycloak to a version that addresses CVE-2023-2585, which implements proper device code and client ID validation in the authorization grant flow.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Single Sign OnApplication
Affected:= 7.6all versions
Openshift Container PlatformApplication
Affected:= 4.11= 4.12
Openshift Container Platform For Ibm ZApplication
Affected:= 4.9= 4.10
Openshift Container Platform For LinuxoneApplication
Affected:= 4.9= 4.10
Openshift Container Platform For PowerApplication
Affected:= 4.9= 4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Keycloak or RH SSO installation
    Locate the Keycloak or Red Hat Single Sign-On service in your environment. Check for processes named 'keycloak', 'jboss', or 'rh-sso', or look for the service listening on common Keycloak ports (8080, 8443). In OpenShift, check for Keycloak or RH SSO pods in the openshift-authentication namespace.
    Affected if Keycloak or RH SSO is present and the version matches the affected range (RH SSO 7.6 all versions, OCP 4.9-4.12).
  2. Determine installed Keycloak/RH SSO version
    For standalone Keycloak, check the version in the server startup logs or the JAR file manifest. For RH SSO in OpenShift, run 'oc get authenticationoperator -o jsonpath='{.items[0].status.version}'' or inspect the RH SSO operator version. Compare this version against the affected versions: RH SSO = 7.6 (all versions), OCP = 4.9, 4.10, 4.11, or 4.12.
    Affected if The installed version falls within the affected ranges listed above.
  3. Check if device authorization grant is enabled
    Inspect the Keycloak/RH SSO realm settings or client configurations. Look for clients with 'Device' grant type enabled, or check the OAuth2 device authorization endpoint (/device) availability. In OpenShift, examine the OAuth configuration: 'oc get oauth cluster -o json' and look for any identity providers configured with device flow capabilities.
    Affected if Device authorization grant flow is enabled or in use, making the validation flaw applicable to your environment.
  4. Review recent authentication logs for suspicious device flow activity
    Examine Keycloak/RH SSO authentication logs for unusual device authorization requests. Look for device_code authorization attempts with mismatched client_id values, or consent prompts for unknown/attackee-controlled clients. Search for patterns like 'Device code validation failed' or unexpected consent approval events.
    Affected if Log analysis reveals device flow authorization requests with client ID mismatches or consent prompts for unrecognized OAuth clients.

You are affected if Keycloak or RH SSO is running with a version in the affected ranges (RH SSO 7.6 all versions, OCP 4.9-4.12) and the device authorization grant flow is enabled or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patch or upgrade Keycloak to a version that addresses CVE-2023-2585, which implements proper device code and client ID validation in the authorization grant flow.

Fix this in Single Sign On Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2585 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data