CVE-2012-5563: Medium severity red hat openstack folsom vulnerability

Published Dec 18, 2012
·
Updated

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.

Affected Software

2 affected componentsFixes available
pip/keystone<8.0.0
8.0.0
Openstack folsom=2012.2

Event History

Dec 18, 2012
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
May 17, 2022
Advisory Published
01:39 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-5563?

CVE-2012-5563 is considered a high severity vulnerability due to its potential to allow unauthorized access through token chaining.

2

How do I fix CVE-2012-5563?

To fix CVE-2012-5563, upgrade OpenStack Keystone to version 8.0.0 or later.

3

Who is affected by CVE-2012-5563?

CVE-2012-5563 affects users running OpenStack Folsom version 2012.2 and earlier versions of Keystone.

4

What can happen if CVE-2012-5563 is exploited?

Exploiting CVE-2012-5563 allows remote authenticated users to bypass authorization restrictions, potentially leading to unauthorized data access.

5

Is CVE-2012-5563 a known issue in OpenStack?

Yes, CVE-2012-5563 is recognized as a vulnerability in OpenStack Keystone, linked to a regression in CVE-2012-3426.

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