Cross-organization authentication via unchecked OAuth application scope
Published Jun 12, 2024 · Updated Aug 2, 2024
Weak authentication in Red Hat Quay allows remote authenticated users to authenticate to applications from inaccessible organizations. The OAuth application flow accepts a valid token paired with an application's client ID without confirming that the token holder can access the organization that created the application. The attacker must obtain the client ID and a usable OAuth token; effects are confined to endpoints that treat authentication alone as sufficient.
Summary
What happened
Weak authentication in Red Hat Quay allows remote authenticated users to authenticate to applications from inaccessible organizations. The OAuth application flow accepts a valid token paired with an application's client ID without confirming that the token holder can access the organization that created the application. The attacker must obtain the client ID and a usable OAuth token; effects are confined to endpoints that treat authentication alone as sufficient.
The record
- CVE
- CVE-2024-5891
- Published
- Jun 12, 2024
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1390, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2024CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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