dbcve.org
KeycloakApplication · Redhat

CVE-2023-6291

HIGH · 7.1 CVSS v3.1 Published 2024-01-26
Fix available
A fix is available. Upgrade to 22.0.7 or later.
See remediation →
78/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
A flaw was found in the redirect_uri validation logic in Keycloak. This issue may allow a bypass of otherwise explicitly allowed hosts. A successful attack may lead to an access token being stolen, making it possible for the attacker to impersonate other users.

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

A validation flaw in Keycloak's redirect_uri logic allows attackers to bypass explicitly allowed host restrictions, potentially enabling theft of access tokens and user impersonation.

MitigationApply the vendor-supplied patch or upgrade Keycloak to the fixed version, and audit all registered redirect URIs for any unauthorized or suspicious entries.

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:< 22.0.7
Single Sign OnApplication
Affected:all versions= 7.6
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
Migration Toolkit For ApplicationsApplication
Affected:= 6.0= 7.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 if Keycloak or RHSSO is deployed
    Check running processes or installed packages for keycloak, rh-sso, or jboss-based services. Look for the Keycloak administration console or known installation paths like /opt/keycloak or /opt/rh/sso.
    Affected if Keycloak or Red Hat Single Sign-On is installed and running
  2. Determine the installed Keycloak version
    Run 'kc.sh --version' from the Keycloak bin directory, or check the server logs for the startup version banner. For RHSSO, check the RPM package version with 'rpm -qa | grep sso' or inspect the server's version endpoint.
    Affected if The version is lower than 22.0.7, or for RHSSO any version indicates potential exposure
  3. Identify OAuth2/OpenID clients configured in Keycloak
    Log into the Keycloak admin console and navigate to Clients under each realm, or query the realm-client endpoint via REST API to list all registered clients.
    Affected if Any OAuth2 or OpenID clients are registered in Keycloak realms
  4. Review registered redirect URIs for clients
    In the admin console, select each client and inspect the Valid Redirect URIs field. Look for entries containing wildcards (*), multiple host patterns, or URIs referencing untrusted domains.
    Affected if Any client has a redirect URI pattern that allows arbitrary hosts or uses wildcard configurations like '*' or 'https://*.example.com'
  5. Check for client configurations using relative paths
    Inspect the Valid Redirect URIs field in client settings. Identify any entries that are relative paths or lack an explicit scheme and host restriction.
    Affected if Clients use relative or loosely restricted redirect URI patterns that could be exploited
  6. Audit client credentials and grant settings
    Review each client's configuration for Enabled (must be ON), Standard Flow Enabled, and Direct Access Grants Enabled. Check if any client uses public access type with sensitive scopes.
    Affected if Clients with public access type and broad OAuth scopes are present alongside the vulnerable redirect URI configuration

A user is affected if they run a version of Keycloak below 22.0.7 or any version of RHSSO and have OAuth2 clients with loosely configured or wildcard redirect URIs that could be exploited.

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 22.0.7 or later
Fixed in 22.0.7
Interim mitigation

Apply the vendor-supplied patch or upgrade Keycloak to the fixed version, and audit all registered redirect URIs for any unauthorized or suspicious entries.

Recommended fix High confidence

Keycloak 22.0.7 or later

  1. 1. Identify all Keycloak instances currently running versions prior to 22.0.7
  2. 2. Review the Keycloak 22.0.7 release notes and migration guide for any breaking changes relevant to your deployment
  3. 3. Create a backup of your current Keycloak configuration, database, and realm data
  4. 4. Test the upgrade in a non-production environment first to validate compatibility with your custom themes, extensions, and integrations
  5. 5. Schedule a maintenance window for the production upgrade
  6. 6. Stop the running Keycloak services
  7. 7. Upgrade Keycloak to version 22.0.7 or later following the official upgrade documentation
  8. 8. Verify that the redirect_uri validation is working correctly by testing known redirect scenarios
Caveat Review Keycloak 22.x migration guide; custom themes, extensions, or deprecated APIs may require updates

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

Fix this in Keycloak Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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