dbcve.org
KeycloakApplication · Redhat

CVE-2023-0264

MEDIUM · 5.0 CVSS v3.1 Published 2023-08-04
Fix available
A fix is available. Upgrade to 7.6.2 / 18.0.6 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A flaw was found in Keycloaks OpenID Connect user authentication, which may incorrectly authenticate requests. An authenticated attacker who could obtain information from a user request within the same realm could use that data to impersonate the victim and generate new session tokens. This issue could impact confidentiality, integrity, and availability.

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 · moderate confidence

Keycloak's OpenID Connect implementation contains a session impersonation flaw where an authenticated attacker within the same realm who obtains certain information from a user request can impersonate the victim and generate new session tokens, enabling unauthorized access to the victim's sessions.

MitigationUpgrade Keycloak to the patched version and review/rotate existing sessions to ensure compromised sessions are invalidated.

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
KeycloakApplication
Affected:< 18.0.6
Single Sign OnApplication
Affected:< 7.6.2all versions
Openshift Container PlatformApplication
Affected:= 4.9= 4.10
Openshift Container Platform For Ibm LinuxoneApplication
Affected:= 4.9= 4.10
Openshift Container Platform Ibm Z SystemsApplication
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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 and version
    Check the installed version of Keycloak or Red Hat Single Sign-On. For Keycloak, run: 'keycloak --version' or check the pom.xml/build.gradle if source available. For RH SSO, check via RPM: 'rpm -qi rh-sso7-keycloak' or check the server version via admin console at /auth/realms/master/. Look for the version number in the response.
    Affected if The installed version is below 18.0.6 for Keycloak, or below 7.6.2 for Red Hat Single Sign-On (all versions of RH SSO prior to 7.6.2 are affected).
  2. Identify OpenShift Container Platform with integrated Keycloak
    If Keycloak is deployed on OCP, check the OCP version by running: 'oc get clusterversion' or 'oc version'. Identify any Keycloak pods in the cluster using: 'oc get pods -A | grep -i keycloak' or check for the Keycloak operator.
    Affected if OCP versions 4.9 or 4.10 are running with Keycloak integrated for authentication.
  3. Verify OpenID Connect realm is configured
    Access the Keycloak/RH SSO admin console and navigate to the Realm Settings or examine the realm configuration files (typically in /opt/keycloak/standalone/data/keycloakdb/ or the database). Check if OpenID Connect (OIDC) adapters or clients are configured for any realm.
    Affected if OpenID Connect realms or clients are configured and active, enabling the attack surface for session impersonation.
  4. Review active user sessions for anomalies
    In the Keycloak/RH SSO admin console, go to Sessions under the Realm or specific client. Check for any sessions created in short succession, sessions with unusual client IPs, or sessions that the user does not recognize. Alternatively, query session tables in the underlying database for duplicate or overlapping session IDs.
    Affected if Unexpected or unauthorized sessions exist that were not initiated by legitimate users, indicating potential exploitation.

Your environment is affected if you are running any Keycloak version below 18.0.6, any RH SSO version below 7.6.2, or OCP versions 4.9 or 4.10 with integrated Keycloak, and you have OpenID Connect realms configured.

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.

dbcve · scoped
Upgrade available Upgrade to 7.6.2 / 18.0.6 or later
Fixed in 7.6.218.0.6
Interim mitigation

Upgrade Keycloak to the patched version and review/rotate existing sessions to ensure compromised sessions are invalidated.

Recommended fix High confidence

Keycloak 18.0.6 or RH-SSO 7.6.2

  1. Upgrade Keycloak to version 18.0.6 or later
  2. If using Red Hat Single Sign-On (RH-SSO), upgrade to version 7.6.2 or later
  3. For OpenShift Container Platform deployments, apply the corresponding Red Hat security advisory patches for OCP 4.9 and 4.10 once available via your OCP cluster management tools
  4. After upgrading, verify that existing user sessions are still valid and consider invalidating potentially compromised sessions if there is evidence of exploitation
  5. Test the authentication flow thoroughly to confirm the vulnerability is remediated
Caveat Review Keycloak 18.x release notes for any breaking changes from your current version; ensure compatibility with your existing realm configurations and custom themes before upgrading production instances

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keycloak Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0264 — 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-0264 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