CVE-2013-2104: High severity openstack keystone vulnerability
python-keystoneclient before 0.2.4, as used in OpenStack Keystone (Folsom), does not properly check expiry for PKI tokens, which allows remote authenticated users to (1) retain use of a token after it has expired, or (2) use a revoked token once it expires.
Other sources
Thierry Carrez (thierry) reports:
Title: Missing expiration check in Keystone PKI token validation Reporter: Eoghan Glynn (Red Hat) Products/Affects: Keystone (Folsom only), python-keystoneclient (0.2.0+)
Description: Eoghan Glynn from Red Hat reported a vulnerability in expiry checks for PKI tokens in the Keystone authentication middleware. Expired tokens for authenticated users could continue to be used, potentially resulting in the bypass of intended security policies. The effect of PKI token revocation is also reversed when the token expires, in the sense that a revoked token is once again treated as being valid. Only setups using PKI tokens are affected.
Note: The affected code was added to Keystone in the Folsom release, but was moved to python-keystoneclient during the Grizzly development cycle.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2013-2104?
CVE-2013-2104 is considered a medium severity vulnerability due to its potential impact on user access management.
How do I fix CVE-2013-2104?
To fix CVE-2013-2104, upgrade python-keystoneclient to version 0.2.4 or later.
What products are affected by CVE-2013-2104?
CVE-2013-2104 affects versions of python-keystoneclient up to 0.2.3 and specifically 0.2.2.
What are the risks of using an affected version of python-keystoneclient in CVE-2013-2104?
Using an affected version of python-keystoneclient may allow users to use expired or revoked PKI tokens, compromising access controls.
Who reported the CVE-2013-2104 vulnerability?
The vulnerability was reported by Thierry Carrez.