Keystone PKI tokens validation Missing expiration check

2013.05.29
Credit: Eoghan Glynn
Risk: Medium
Local: Yes
Remote: No
CWE: CWE-264


CVSS Base Score: 5.5/10
Impact Subscore: 4.9/10
Exploitability Subscore: 8/10
Exploit range: Remote
Attack complexity: Low
Authentication: Single time
Confidentiality impact: None
Integrity impact: Partial
Availability impact: Partial

OpenStack Security Advisory: 2013-014 CVE: CVE-2013-2104 Date: May 28, 2013 Title: Missing expiration check in Keystone PKI tokens validation Reporter: Eoghan Glynn (Red Hat), Alex Meade (Rackspace) Products/Affects: Keystone (Folsom only), python-keystoneclient (0.2.0+) Description: Eoghan Glynn from Red Hat and Alex Meade from Rackspace both 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. python-keystoneclient fix (will be included in upcoming 0.2.4 release): https://review.openstack.org/#/c/30742/ Keystone (Folsom) fix: https://review.openstack.org/#/c/30743/ References: https://bugs.launchpad.net/python-keystoneclient/+bug/1179615 http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2013-2104

References:

https://bugs.launchpad.net/python-keystoneclient/+bug/1179615
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2013-2104
https://review.openstack.org/#/c/30743/


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top