Privilege escalation via ignored OAuth1 role restrictions
Published May 6, 2020 · Updated Aug 4, 2024
Authorization bypass in OpenStack Keystone before 15.0.1 and 16.0.0 allows remote authenticated users to obtain unintended project roles. The OAuth1 Token API discards the role subset supplied during request-token authorization, so token exchange includes every project role held by the authorizing user. Exploitation requires OAuth1 to be enabled and a user with multiple project roles to authorize a consumer; the resulting token can exercise roles that the user withheld.
Summary
What happened
Authorization bypass in OpenStack Keystone before 15.0.1 and 16.0.0 allows remote authenticated users to obtain unintended project roles. The OAuth1 Token API discards the role subset supplied during request-token authorization, so token exchange includes every project role held by the authorizing user. Exploitation requires OAuth1 to be enabled and a user with multiple project roles to authorize a consumer; the resulting token can exercise roles that the user withheld.
The record
- CVE
- CVE-2020-12690
- Published
- May 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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