dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2024-8883

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 misconfiguration flaw was found in Keycloak. This issue can allow an attacker to redirect users to an arbitrary URL if a 'Valid Redirect URI' is set to http://localhost or http://127.0.0.1, enabling sensitive information such as authorization codes to be exposed to the attacker, potentially leading to session hijacking.

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 confidence

Keycloak contains a misconfiguration where Valid Redirect URIs are set to generic http://localhost or http://127.0.0.1 patterns instead of specific absolute URLs. This allows an attacker to craft malicious links using these allowed prefixes to redirect users to arbitrary external sites after authentication, potentially intercepting authorization codes during the OAuth flow and enabling session hijacking.

MitigationUpdate all Keycloak client configurations to use specific, absolute HTTPS redirect URIs rather than generic localhost/127.0.0.1 patterns, and properly constrain the 'Web Origins' setting to prevent CORS-based token leakage.

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
Affected:all versions
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
Single Sign OnApplication
Affected:all versions= 7.6

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Keycloak version
    Access the Keycloak admin console or use the REST API endpoint /admin/realms/{realm} to retrieve server info. Check the 'version' field in the response.
    Affected if The installed version falls within any of the affected product ranges listed in the CVE (all versions of Redhat Build of Keycloak, Redhat Single Sign On, or specific versions of Redhat Openshift Container Platform).
  2. List all client configurations
    Use the Keycloak Admin API: GET /admin/realms/{realm}/clients or navigate to the 'Clients' section in the admin console. Retrieve the 'redirectUris' array for each client.
    Affected if Any client has a redirect URI that begins with http://localhost or http://127.0.0.1 (with or without port numbers) rather than a specific absolute HTTPS URL.
  3. Inspect Web Origins configuration
    For each client, check the 'webOrigins' field in the client configuration. Navigate to Client Settings > Advanced Settings > Web Origins in the admin console.
    Affected if Web Origins is set to '*' (wildcard) or includes origins that could allow CORS-based token leakage in conjunction with the vulnerable redirect URIs.

You are affected if your Keycloak version matches the affected product ranges AND any client has redirect URIs configured with generic http://localhost or http://127.0.0.1 patterns instead of specific absolute HTTPS URLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all Keycloak client configurations to use specific, absolute HTTPS redirect URIs rather than generic localhost/127.0.0.1 patterns, and properly constrain the 'Web Origins' setting to prevent CORS-based token leakage.

Recommended fix High confidence
  1. 1. Access the Keycloak Admin Console and navigate to the Realm Settings > Login Settings section.
  2. 2. Review all clients and identify any 'Valid Redirect URI' or 'Base URL' settings that are configured to http://localhost or http://127.0.0.1.
  3. 3. For each affected client, update the 'Valid Redirect URI' to use a specific, fully qualified domain name (e.g., https://your-domain.com/*) instead of localhost or 127.0.0.1.
  4. 4. Ensure the redirect URIs follow the principle of least privilege - only allow specific, expected redirect URLs rather than wildcard patterns if possible.
  5. 5. After making changes, test the authentication flow to verify redirects work correctly for legitimate users.
  6. 6. Document the corrected redirect URI configuration in client documentation to prevent regression.

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

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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