Strix
26.1K

CVE-2012-3426

UnknownEPSS 2.27%

Last modified

CVE-2012-3426 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.27% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
2.27%

80.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpenstackEssexAll versions
OpenstackHorizonfolsom-1
OpenstackKeystone2012.1
OpenstackKeystone2012.1.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2012-3426?
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.
How severe is CVE-2012-3426?
Severity scoring for CVE-2012-3426 is pending analysis. The EPSS model estimates a 2.27% probability of exploitation in the next 30 days.
How do I fix CVE-2012-3426?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2012-3426?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST