Authenticated cross-project control via universal member assignment
Published Jan 17, 2020 · Updated Sep 17, 2024
Improper authorization in SUSE OpenStack Cloud 8 allows remote authenticated users to access and control resources in every project. The keystone-json-assignment backend treats every account named in /etc/keystone/user-project-map.json as a member of every project instead of limiting membership to the configured mapping. An account must be present in that mapping and authenticate to Keystone; it can then read, modify, create, or delete arbitrary cloud resources.
Summary
What happened
Improper authorization in SUSE OpenStack Cloud 8 allows remote authenticated users to access and control resources in every project. The keystone-json-assignment backend treats every account named in /etc/keystone/user-project-map.json as a member of every project instead of limiting membership to the configured mapping. An account must be present in that mapping and authenticate to Keystone; it can then read, modify, create, or delete arbitrary cloud resources.
The record
- CVE
- CVE-2019-3683
- Published
- Jan 17, 2020
- Updated
- Sep 17, 2024
- Vendor
- SUSE
- Product
- SUSE OpenStack Cloud
- Classifications
- CWE-732, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2020CVE publishedPublication date reported by the CVE source.
- Sep 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=keystone-json-assignment <d7888c75505465490250c00cc0ef4bb1af662f9f
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