CVE-2013-2059: Medium severity keystone vulnerability

Published May 21, 2013
·
Updated

OpenStack Identity (Keystone) Folsom 2012.2.4 and earlier, Grizzly before 2013.1.1, and Havana does not immediately revoke the authentication token when deleting a user through the Keystone v2 API, which allows remote authenticated users to retain access via the token.

Affected Software

3 affected componentsFixes available
pip/keystone<8.0.0a0
8.0.0a0
Openstack Keystone=2012.1
Openstack Keystone=2013.1

Event History

May 21, 2013
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·01:36 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-2013-2059?

CVE-2013-2059 is considered a medium severity vulnerability due to the potential for unauthorized access to user accounts.

2

How do I fix CVE-2013-2059?

To fix CVE-2013-2059, users should upgrade to OpenStack Keystone version 2013.1.1 or later.

3

What is the impact of CVE-2013-2059?

The impact of CVE-2013-2059 allows remote authenticated users to retain access to the system even after their user account has been deleted.

4

Which versions are affected by CVE-2013-2059?

CVE-2013-2059 affects OpenStack Identity (Keystone) versions 2012.2.4 and earlier, Grizzly before 2013.1.1, and Havana.

5

Is there a workaround for CVE-2013-2059?

While the primary mitigation for CVE-2013-2059 is upgrading, admins may consider manually revoking tokens when deleting a user as a temporary workaround.

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