First published: Tue Jul 31 2012(Updated: )
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Keystone | <8.0.0a0 | 8.0.0a0 |
OpenStack Essex | ||
OpenStack Horizon | =folsom-1 | |
OpenStack Keystone | =2012.1 | |
OpenStack Keystone | =2012.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-3426 is classified as a moderate severity vulnerability due to improper token expiration handling.
To fix CVE-2012-3426, upgrade to OpenStack Keystone version 2012.1.1 or higher.
CVE-2012-3426 affects OpenStack Keystone versions prior to 2012.1.1 and OpenStack Folsom before Folsom-1.
CVE-2012-3426 allows remote authenticated users to bypass authorization restrictions by creating new tokens through token chaining.
Yes, CVE-2012-3426 specifically impacts OpenStack Keystone before version 2012.1.1 and OpenStack Essex.