Access-token impersonation via unenforced token types
Published Nov 17, 2024 · Updated Nov 17, 2024
Improper access control in Keycloak before 22.0.10 and 23.0.0 through 24.0.2 allows remote authenticated users to obtain access tokens. The broker OIDC signature-validation path accepts a signed logout token without enforcing its token type, then exchanges it as an access credential. Exploitation requires an authenticated session, adjacent network access, and user interaction, and can expose or alter data beyond assigned permissions.
Summary
What happened
Improper access control in Keycloak before 22.0.10 and 23.0.0 through 24.0.2 allows remote authenticated users to obtain access tokens. The broker OIDC signature-validation path accepts a signed logout token without enforcing its token type, then exchanges it as an access credential. Exploitation requires an authenticated session, adjacent network access, and user interaction, and can expose or alter data beyond assigned permissions.
The record
- CVE
- CVE-2023-0657
- Published
- Nov 17, 2024
- Updated
- Nov 17, 2024
- Vendor
- Red Hat
- Product
- Red Hat Single Sign-On 7
- Classifications
- CWE-347, CWE-284, CWE-287, CWE-273, CWE-290, T1550.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 17, 2024CVE publishedPublication date reported by the CVE source.
- Nov 17, 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