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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2012-0015 | 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. |
Github GHSA |
GHSA-xp97-6w7r-4cjc | OpenStack Keystone token expiration issues |
Ubuntu USN |
USN-1552-1 | OpenStack Keystone vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-06T20:05:12.524Z
Reserved: 2012-06-14T00:00:00
Link: CVE-2012-3426
No data.
Status : Deferred
Published: 2012-07-31T10:45:42.670
Modified: 2025-04-11T00:51:21.963
Link: CVE-2012-3426
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA
Ubuntu USN