OpenStack Keystone token expiration issues
Published Jul 31, 2012 · Updated Oct 23, 2026 · Also known as GHSA-xp97-6w7r-4cjc
Original summary
Normalized public record · Updated Oct 23, 2026
OpenStack Keystone token expiration issues
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-xp97-6w7r-4cjc
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Patch commit ↗
- Patch commit ↗
- bugs.launchpad.net ↗
- bugs.launchpad.net ↗
- launchpad.net ↗
- 50494 ↗
- Patch commit ↗
- bugs.launchpad.net ↗
- [oss-security] 20120727 [OSSA 2012-010] Various Keystone token expiration issues (CVE-2012-3426) ↗
- Patch commit ↗
- USN-1552-1 ↗
- Patch commit ↗
Record history
Published Jul 31, 2012 · Last refreshed Oct 23, 2026