First published: Tue May 21 2013(Updated: )
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.
Affected Software | Affected Version | How to fix |
---|---|---|
OpenStack keystonemiddleware | ||
OpenStack Keystone | >=0.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-965852 is considered critical due to the missing expiration check in Keystone PKI token validation.
To fix REDHAT-BUG-965852, update to the latest version of OpenStack Keystone and python-keystoneclient that includes the patch addressing the expiration check.
REDHAT-BUG-965852 affects OpenStack Keystone Folsom only and python-keystoneclient versions 0.2.0 and above.
The implications of REDHAT-BUG-965852 include potential unauthorized access due to the lack of expiration checks on PKI tokens.
REDHAT-BUG-965852 was reported by Eoghan Glynn from Red Hat.