An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2020/05/07/3 | Mailing List Third Party Advisory |
https://bugs.launchpad.net/keystone/+bug/1873290 | Patch Third Party Advisory |
https://lists.apache.org/thread.html/re237267da268c690df5e1c6ea6a38a7fc11617725e8049490f58a6fa%40%3Ccommits.druid.apache.org%3E | |
https://lists.apache.org/thread.html/re4ffc55cd2f1b55a26e07c83b3c22c3fe4bae6054d000a57fb48d8c2%40%3Ccommits.druid.apache.org%3E | |
https://security.openstack.org/ossa/OSSA-2020-005.html | Vendor Advisory |
https://usn.ubuntu.com/4480-1/ | |
https://www.openwall.com/lists/oss-security/2020/05/06/6 | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2020-05-07 00:15
Updated : 2023-11-07 03:15
NVD link : CVE-2020-12690
Mitre link : CVE-2020-12690
CVE.ORG link : CVE-2020-12690
JSON object : View
Products Affected
openstack
- keystone
CWE
CWE-613
Insufficient Session Expiration