CVE-2024-2419
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 · uneditedA flaw was found in Keycloak's redirect_uri validation logic. This issue may allow a bypass of otherwise explicitly allowed hosts. A successful attack may lead to the theft of an access token, making it possible for the attacker to impersonate other users. It is very similar to CVE-2023-6291.
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's OAuth/OpenID Connect redirect_uri validation contains a bypass vulnerability in its allowlist logic. An attacker can craft a malicious redirect URI that bypasses explicitly allowed host restrictions, potentially redirecting authorization codes or tokens to an attacker-controlled endpoint. This enables token theft and user impersonation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Keycloak installation versionCheck your Keycloak instance version by accessing the server info endpoint (e.g., /realms/master/server-info) or reviewing the server logs at startup. On the server, you can also check the pom.xml or the version file in the installation directory.Affected if The installed version falls within the vulnerable range and is unpatched.
-
Locate OAuth2/OIDC client configurationsIn the Keycloak admin console, navigate to the 'Clients' section for each realm. Alternatively, query the realm-client endpoint via the admin REST API (GET /{realm}/clients) to list all registered clients.Affected if Clients are configured with redirect_uri settings.
-
Examine redirect_uri allowlist patternsFor each client, review the 'Valid Redirect URIs' field. Look for redirect_uri values containing wildcards, multiple path segments, or unusual domain patterns that may bypass host restrictions.Affected if Any redirect_uri contains patterns that could potentially circumvent host allowlist validation.
-
Verify redirect_uri validation behaviorTest the OAuth authorization flow with a crafted redirect_uri that includes an allowed host prefix followed by a malicious domain (e.g., https://allowed-host.attacker.com). Observe whether Keycloak accepts this redirect.Affected if Keycloak accepts a redirect_uri that redirects to a domain not explicitly in the allowlist.
You are affected if your Keycloak version contains the vulnerability and you have OAuth/OIDC clients with redirect_uri configurations that could be bypassed.
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.
From vendor dataUpdate Keycloak to the version containing the fix for CVE-2024-2419, or apply any available patches. Review and audit existing client configurations for suspicious redirect_uri patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2419 — 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-2419 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