CVE-2012-3426: Medium severity Openstack Essex vulnerability

Published Jul 31, 2012
·
Updated

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.

Affected Software

5 affected componentsFixes available
pip/Keystone<8.0.0a0
8.0.0a0
Openstack Essex
Openstack Horizon=folsom-1
Openstack Keystone=2012.1
Openstack Keystone=2012.1.1

Event History

Jul 31, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
May 17, 2022
Advisory Published
via GitHub·05:23 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-3426?

CVE-2012-3426 is classified as a moderate severity vulnerability due to improper token expiration handling.

2

How do I fix CVE-2012-3426?

To fix CVE-2012-3426, upgrade to OpenStack Keystone version 2012.1.1 or higher.

3

What systems are affected by CVE-2012-3426?

CVE-2012-3426 affects OpenStack Keystone versions prior to 2012.1.1 and OpenStack Folsom before Folsom-1.

4

What type of attack does CVE-2012-3426 allow?

CVE-2012-3426 allows remote authenticated users to bypass authorization restrictions by creating new tokens through token chaining.

5

Is CVE-2012-3426 specific to certain OpenStack versions?

Yes, CVE-2012-3426 specifically impacts OpenStack Keystone before version 2012.1.1 and OpenStack Essex.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203