OpenStack Keystone Insufficient token expiration
OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2012-5563US | medium4.0OT elevated | — | ||
OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restr… | ||||
02
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2012-1557.htmlWEB
- http://www.openwall.com/lists/oss-security/2012/11/28/5WEB
- http://www.openwall.com/lists/oss-security/2012/11/28/6WEB
- http://www.ubuntu.com/usn/USN-1641-1WEB
- https://bugs.launchpad.net/keystone/+bug/1079216WEB
- https://exchange.xforce.ibmcloud.com/vulnerabilities/80370WEB
- https://github.com/openstack/keystonePACKAGE
- https://github.com/openstack/keystone/commit/38c7e46a640a94da4da89a39a5a1ea9c081f1eb5WEB
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