OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2012-3426US | medium4.9 | — | ||
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated… | ||||
02
references
External citations — patches, advisories, analysis.
- http://github.com/openstack/keystone/commit/29e74e73a6e51cffc0371b32354558391826a4aaFIX
- http://github.com/openstack/keystone/commit/375838cfceb88cacc312ff6564e64eb18ee6a355FIX
- http://github.com/openstack/keystone/commit/628149b3dc6b58b91fd08e6ca8d91c728ccb8626FIX
- http://github.com/openstack/keystone/commit/a67b24878a6156eab17b9098fa649f0279256f5dFIX
- http://github.com/openstack/keystone/commit/d9600434da14976463a0bd03abd8e0309f0db454FIX
- http://github.com/openstack/keystone/commit/ea03d05ed5de0c015042876100d37a6a14bf56deFIX
- http://secunia.com/advisories/50045ADVISORY
- http://secunia.com/advisories/50494ADVISORY
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