An issue was discovered in OpenStack Keystone before 29.0.2.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 27.0.2, 28.0.2, 29.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone federated token rescoping mechanism does not propagate the original token's expiry to the newly issued token. When a federated user rescopes a token via POST /v3/auth/tokens, the handle_scoped_token() function in the mapped authentication plugin returns response data without an expires_at value. The token provider falls back to issuing a token with a fresh default TTL. By rescoping repeatedly before each token expires, a user can maintain access indefinitely, bypassing operator-configured token lifetime policies. This is a variant of CVE-2012-3426. Only deployments using federated identity (SAML2, OpenID Connect) are affected.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- OpenStack Keystone
From 14.0.0 · fixed in 27.0.2; From 28.0.0 · fixed in 28.0.2; From 29.0.0 · fixed in 29.0.2
- keystonePyPI
From 14.0.0 · fixed in 27.0.2
- keystonePyPI
From 28.0.0 · fixed in 28.0.2
- keystonePyPI
From 29.0.0 · fixed in 29.0.2
- keystonePyPI
From 14.0.0 · fixed in 27.0.2; From 28.0.0 · fixed in 28.0.2; From 29.0.0 · fixed in 29.0.2