OpenStack Keystone Insufficient token expiration
Published Dec 18, 2012 · Updated Oct 23, 2026 · Also known as GHSA-w66p-78g4-mr7g, PYSEC-2012-20
Original summary
Normalized public record · Updated Oct 23, 2026
OpenStack Keystone Insufficient token expiration
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression.
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-w66p-78g4-mr7g, PYSEC-2012-20
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2012:1557 ↗
- [oss-security] 20121128 [OSSA 2012-018] EC2-style credentials invalidation issue (CVE-2012-5571) ↗
- Patch commit ↗
- 56727 ↗
- USN-1641-1 ↗
- Patch commit ↗
- [oss-security] 20121128 [OSSA 2012-019] Extension of token validity through token chaining (CVE-2012-5563) ↗
- bugs.launchpad.net ↗
- 51423 ↗
- folsom-tokens-security-bypass(80370) ↗
- 51436 ↗
Record history
Published Dec 18, 2012 · Last refreshed Oct 23, 2026