From ${URL} : Thierry Carrez (thierry@openstack.org) 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. @maintainer(s): after the bump, in case we need to stabilize the package, please say explicitly if it is ready for the stabilization or not.
I already fixed sys-auth/keystone (check the changelog). As far as python-keystoneclient goes, they haven't released a patch against 0.2.3. If anyone can generate a patchset for it I'm all ears :D.
fully fixed in both sys-auth/keystone-2012.2.4-r4 and dev-python/keystoneclient-0.2.4
It's been fixed, no vulnerable ebuilds in tree. Closing noglsa.