Account takeover via cross-user session identifier reuse
Published Apr 25, 2024 · Updated Nov 11, 2025
Improper authentication in Keycloak before 22.0.10 and before 24.0.3 allows remote attackers to hijack active user sessions. The re-authentication path retains the prior session identifier when prompt=login is followed by credential entry and Restart login, allowing a session with a different subject to share that identifier. Exploitation requires user interaction with the forced re-authentication flow; successful exploitation grants access under the prior active session.
Summary
What happened
Improper authentication in Keycloak before 22.0.10 and before 24.0.3 allows remote attackers to hijack active user sessions. The re-authentication path retains the prior session identifier when prompt=login is followed by credential entry and Restart login, allowing a session with a different subject to share that identifier. Exploitation requires user interaction with the forced re-authentication flow; successful exploitation grants access under the prior active session.
The record
- CVE
- CVE-2023-6787
- Published
- Apr 25, 2024
- Updated
- Nov 11, 2025
- Vendor
- Red Hat
- Product
- Red Hat Single Sign-On 7
- Classifications
- CWE-287, CWE-613, CWE-384, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Nov 11, 2025Record 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?
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