First published: Tue Apr 01 2014(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
OpenStack Keystone | =2013.1 | |
OpenStack Keystone | =2013.1.1 | |
OpenStack Keystone | =2013.1.2 | |
OpenStack Keystone | =2013.1.3 | |
OpenStack Keystone | =2013.1.4 | |
OpenStack Keystone | =2013.2.2 | |
pip/keystone | <8.0.0a0 | 8.0.0a0 |
=2013.1 | ||
=2013.1.1 | ||
=2013.1.2 | ||
=2013.1.3 | ||
=2013.1.4 | ||
=2013.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-2237 is classified as a medium severity vulnerability.
To fix CVE-2014-2237, you should upgrade to Keystone version 8.0.0a0 or later.
CVE-2014-2237 allows unlisted trust tokens to be issued, which may lead to unauthorized access.
CVE-2014-2237 affects OpenStack Keystone versions 2013.1 through 2013.2.2 and icehouse before icehouse-3.
CVE-2014-2237 can be exploited remotely if impersonation is enabled in the trust token configuration.