🛡️ CVE-2012-3426 — keystone
Description
OpenStack Keystone token expiration issues
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.
Affected software
CVE-2012-3426 is recorded against 1 package.
- keystone (fixed in 8.0.0a0)
Timeline and source
Published on 17 May 2022 and last revised on 22 November 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Web)
bugs.launchpad.net (Web)
bugs.launchpad.net (Web)
bugs.launchpad.net (Web)
github.com (Package)
github.com (Web)
launchpad.net (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| keystone | — | 8.0.0a0 |
References
Similar Threats
- High CVE-2012-3542
- Unknown CVE-2012-4413
- High CVE-2012-5563
- Unknown CVE-2012-5571
- Unknown CVE-2013-1865
More CVE 2012 advisories
Browse all of CVE 2012 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2012-3426?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2012-3426 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.