Build Of KeycloakApplication · Redhat
CVE-2024-1132
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, where it does not properly validate URLs included in a redirect. This issue could allow an attacker to construct a malicious request to bypass validation and access other URLs and sensitive information within the domain or conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field, and requires user interaction within the malicious URL.
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 a URL validation flaw in its OAuth/OpenID Connect redirect URI handling. When clients use wildcards in Valid Redirect URIs, the validation logic can be bypassed, allowing attackers to craft malicious URLs that pass validation but redirect to arbitrary domains or sensitive internal URLs. Exploitation requires tricking a user into interacting with the malicious link.
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
all versions
Jboss Middleware Text Only AdvisoriesApplication
= 1.0
KeycloakApplication
>= 21.1.0, < 22.0.10>= 23.0.0, < 24.0.3
Migration Toolkit For ApplicationsApplication
= 1.0
Migration Toolkit For RuntimesApplication
all versions
Openshift Container PlatformApplication
= 4.11= 4.12
Openshift Container Platform For Ibm ZApplication
= 4.9= 4.10
Openshift Container Platform For LinuxoneApplication
= 4.9= 4.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Keycloak versionAccess the Keycloak admin console and navigate to Server Info > Versions, or use the CLI: 'kc.sh version' or check the pom.xml/build metadata in the installation directoryAffected if The version falls within >= 21.1.0 and < 22.0.10, or >= 23.0.0 and < 24.0.3
-
List all clients with wildcard redirect URIsIn the Keycloak admin console, go to each realm > Clients > select each client and inspect the 'Valid Redirect URIs' field. Look for patterns containing '*' wildcards such as 'https://*.example.com/*' or 'https://example.com/*'Affected if Any client has a Valid Redirect URI containing a wildcard character (*)
-
Inspect specific redirect URI patterns for bypassable constructsReview each wildcard redirect URI pattern for constructs that could be exploited, such as 'https://*.domain.com' which may allow 'https://evil.domain.com.attacker.com' to pass validationAffected if Wildcard patterns use overly broad constructs like '*.domain.com' without additional strict validation rules
-
Verify redirect URI validation behaviorTest the redirect URI validation by attempting to register a redirect URI with variations like 'https://legitimate.com.evil.com' against a pattern 'https://*.legitimate.com/*' if wildcards are in useAffected if The validation incorrectly allows redirect URIs pointing to domains other than those explicitly intended in the wildcard pattern
You are affected if your Keycloak version is in the vulnerable range AND any client is configured with wildcard patterns in Valid Redirect URIs, as the bypass requires wildcard-based redirect URI configuration to be exploitable.
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 · scoped22.0.1024.0.3
Remove wildcard patterns from Valid Redirect URIs and use explicit, specific URI patterns; if wildcards are required, implement strict additional validation or upgrade to the patched Keycloak version.
Keycloak 22.0.10 or Keycloak 24.0.3 (or later in the respective release branches)
- Identify your current Keycloak version by checking the server logs or startup banner
- Determine the appropriate upgrade path based on your current version: if running 21.1.0-21.x, upgrade to 22.0.10 or later; if running 22.x, upgrade to 22.0.10 or later; if running 23.0.0-23.x, upgrade to 24.0.3 or later
- Review the Keycloak upgrade guide for your version at https://www.keycloak.org/guides#server
- Backup your current Keycloak database and configuration before upgrading
- Stop the Keycloak server
- Install the fixed version (22.0.10 or 24.0.3 or later)
- Start the Keycloak server and verify the application starts successfully
- Test that client applications with wildcard redirect URIs function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Of Keycloak
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1132 — 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-1132 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