Cross-client token access via unbound device codes
Published Dec 21, 2023 · Updated Aug 2, 2024
Authentication bypass in Red Hat Single Sign-On 7.6 allows remote authenticated users to obtain access tokens for other OAuth clients. The DeviceGrantType token endpoint loads an OAuth2DeviceCodeModel by device_code without checking that its stored clientId matches the requesting client. Exploitation requires Device Authorization Grant on both clients and a user to approve the supplied user code; success grants the malicious client a token on that user's behalf.
Summary
What happened
Authentication bypass in Red Hat Single Sign-On 7.6 allows remote authenticated users to obtain access tokens for other OAuth clients. The DeviceGrantType token endpoint loads an OAuth2DeviceCodeModel by device_code without checking that its stored clientId matches the requesting client. Exploitation requires Device Authorization Grant on both clients and a user to approve the supplied user code; success grants the malicious client a token on that user's behalf.
The record
- CVE
- CVE-2023-2585
- Published
- Dec 21, 2023
- Updated
- Aug 2, 2024
- Vendor
- Red Hat
- Product
- RHEL-8 based Middleware Containers
- Classifications
- CWE-287, CWE-358, CWE-290, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 21, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
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