Session takeover via reused offline session identifiers
Published Sep 20, 2023 · Updated Aug 3, 2024
Session takeover in Red Hat Single Sign-On allows remote authenticated users to obtain another user's token through offline refresh. Keycloak reuses an identifier between root and user authentication sessions without validating that the root session belongs to the current user. Exploitation requires an offline_access client, a prior user who leaves cookies on a shared device, and a second user who authenticates before refresh-token use.
Summary
What happened
Session takeover in Red Hat Single Sign-On allows remote authenticated users to obtain another user's token through offline refresh. Keycloak reuses an identifier between root and user authentication sessions without validating that the root session belongs to the current user. Exploitation requires an offline_access client, a prior user who leaves cookies on a shared device, and a second user who authenticates before refresh-token use.
The record
- CVE
- CVE-2022-3916
- Published
- Sep 20, 2023
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- RHEL-8 based Middleware Containers
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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