CVE-2012-3426

medium
Published 2012-07-31 ยท Modified 2024-11-22
CVSS v3
โ€”
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
4.9

Description

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.

Predictions

Exploit likelihood
20%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 2012.1.1-1
sid Fixed 2012.1.1-1
forky Fixed 2012.1.1-1
bullseye Fixed 2012.1.1-1
bookworm Fixed 2012.1.1-1

Package impact

EcosystemPackageVulnerableFixed
python PyPIkeystone<8.0.0a08.0.0a0

Application impact

VendorProductVersionsFixed
openstackessex
openstackhorizonfolsom-1
openstackkeystone2012.1
openstackkeystone2012.1.1

References

CWEs

CWE-264

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.