Authorization-code disclosure via loopback redirect validation bypass
Published Sep 19, 2024 · Updated Aug 4, 2026
Open redirect in Keycloak before 22.0.12, 23.0.0 through 24.0.6, and 25.0.0 through 25.0.4 exposes authorization codes to remote attackers. RedirectUtils removes a port-like authority substring before matching a loopback redirect, so localhost:port@attacker-host can match an allowed localhost URI. Exploitation requires a client allowing a localhost or 127.0.0.1 redirect and user authorization, after which the exposed code can enable session hijacking.
Summary
What happened
Open redirect in Keycloak before 22.0.12, 23.0.0 through 24.0.6, and 25.0.0 through 25.0.4 exposes authorization codes to remote attackers. RedirectUtils removes a port-like authority substring before matching a loopback redirect, so localhost:port@attacker-host can match an allowed localhost URI. Exploitation requires a client allowing a localhost or 127.0.0.1 redirect and user authorization, after which the exposed code can enable session hijacking.
The record
- CVE
- CVE-2024-8883
- Published
- Sep 19, 2024
- Updated
- Aug 4, 2026
- Vendor
- Red Hat
- Product
- RHEL-8 based Middleware Containers
- Classifications
- CWE-601
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo