OpenStack Identity (Keystone) Trustee token revocations does not work with memcache backend
The memcache token backend in OpenStack Identity (Keystone) 2013.1 through 2.013.1.4, 2013.2 through 2013.2.2, and icehouse before icehouse-3, when issuing a trust token with impersonation enabled, does not include this token in the trustee's token-index-list, which prevents the token from being invalidated by bulk token revocation and allows the trustee to bypass intended access restrictions.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-2237US | medium5.0 | — | ||
The memcache token backend in OpenStack Identity (Keystone) 2013.1 through 2.013.1.4, 2013.2 through 2013.2.2, and icehouse before icehouse-3, when issuing a trust token with imper… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2014/03/04/16WEB
- https://bugs.launchpad.net/keystone/+bug/1260080WEB
- https://github.com/openstack/keystonePACKAGE
- https://github.com/openstack/keystone/commit/813d1254eb4f7a7d40009b23bbadbc4c5cc5daacWEB
- https://github.com/openstack/keystone/commit/a411c944af78c36f2fdb87d305ba452dc52d7ed3WEB
- https://github.com/openstack/keystone/commit/b6f0e26da0e2ab0892a5658da281a065e668637bWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2014-105.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-2237ADVISORY
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