First published: Wed Sep 04 2013(Updated: )
Thierry Carrez reports: Title: Token revocation failure using Keystone memcache/KVS backends Reporter: Kieran Spear (University of Melbourne) Products: Keystone Affects: Folsom, Grizzly Description: Kieran Spear from the University of Melbourne reported a vulnerability in Keystone memcache and KVS token backends. The PKI token revocation lists stored the entire token instead of the token ID, triggering comparison failures, ultimately resulting in revoked PKI tokens still being considered valid. Only Folsom and Grizzly Keystone setups making use of PKI tokens with the memcache or KVS token backends are affected. Havana setups, setups using UUID tokens, or setups using PKI tokens with the SQL token backend are all unaffected.
Affected Software | Affected Version | How to fix |
---|---|---|
Keystone | >=Folsom<=Grizzly |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1004452 is critical due to token revocation failure, posing significant security risks.
To fix REDHAT-BUG-1004452, upgrade your OpenStack Keystone installation to a version beyond Grizzly.
REDHAT-BUG-1004452 affects OpenStack Keystone versions from Folsom to Grizzly.
The impacted product by REDHAT-BUG-1004452 is OpenStack Keystone when using memcache or KVS backends.
The vulnerability REDHAT-BUG-1004452 was reported by Kieran Spear from the University of Melbourne.