Build Of KeycloakApplication · Redhat
CVE-2024-7260
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 · uneditedAn open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referrer_uri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirect_uri using URL encoding, to hide the text of the actual malicious website domain.
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 confidenceKeycloak contains an open redirect vulnerability where specially crafted URLs with manipulated referrer and referrer_uri parameters can redirect users to malicious websites. The vulnerability exploits the trust users place in legitimate Keycloak URLs, enabling phishing attacks and potential bypass of OAuth redirect_uri validation. URL encoding can obfuscate the malicious destination.
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
Build Of KeycloakApplication
< 24.0.7
KeycloakApplication
< 24.0.7CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Keycloak versionLog into the Keycloak Administration Console and navigate to 'Server Info' > 'Versions', or run 'kcadm.sh get server-info' from the bin directory to retrieve the installed version.Affected if The installed version is lower than 24.0.7 for Red Hat Keycloak or Red Hat Build of Keycloak.
-
Confirm Keycloak product variantIn the Administration Console, check the 'System Info' page or server logs at startup to identify whether the deployment uses 'Red Hat Keycloak' or 'Red Hat Build of Keycloak'.Affected if The product is Red Hat Keycloak or Red Hat Build of Keycloak with a version below 24.0.7.
-
Inspect OAuth redirect_uri validation settingsNavigate to 'Realm Settings' > 'Redirect URIs' in the Administration Console and review the configured redirect URIs for client applications.Affected if Redirect URIs are configured but the referrer or referrer_uri parameters in authentication requests can override or bypass these settings.
-
Review referrer header processingExamine the Keycloak server configuration files (standalone.xml or keycloak.conf) for any settings related to 'referrer' or 'referrer_uri' handling, and check authentication flow logs for redirect parameter usage.Affected if The server processes referrer or referrer_uri parameters without strict validation against an allowlist of permitted domains.
You are affected if you are running Red Hat Keycloak or Red Hat Build of Keycloak with a version lower than 24.0.7 and your applications rely on referrer or referrer_uri parameters for redirection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.0.7
Implement strict validation of redirect_uri parameters against an allowlist of permitted domains, and disable or sanitize the referrer/referrer_uri parameters to prevent external redirect manipulation.
Keycloak 24.0.7 or later
- Identify the current Keycloak version in use by checking the Keycloak server status or configuration files
- Download Keycloak version 24.0.7 or later from the official Keycloak releases (https://github.com/keycloak/keycloak/releases)
- Review the Keycloak upgrade guide for migration steps between your current version and 24.0.7
- Back up the current Keycloak database and configuration files
- Stop the running Keycloak instance
- Install Keycloak 24.0.7 (or latest stable version) following the installation guide
- Migrate the database schema if required using the migration scripts provided in the upgrade documentation
- Update any custom themes, extensions, or integrations that may be affected by the version change
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Of Keycloak
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-7260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7260 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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