Insufficient Session Expiration in OpenStack Keystone
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-12690US | high8.8 | — | ||
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 us… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2020/05/07/3WEB
- https://bugs.launchpad.net/keystone/+bug/1873290WEB
- https://github.com/advisories/GHSA-6m8p-x4qw-gh5jADVISORY
- https://github.com/openstack/keystonePACKAGE
- https://github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2020-54.yamlWEB
- https://lists.apache.org/thread.html/re4ffc55cd2f1b55a26e07c83b3c22c3fe4bae6054d000a57fb48d8c2@%3Ccommits.druid.apache.org%3EWEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-12690ADVISORY
- https://security.openstack.org/ossa/OSSA-2020-005.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan