CVE-2013-2030: Medium severity openstack compute (nova) vulnerability

Published Apr 30, 2013
·
Updated

keystone/middleware/authtoken.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by pre-creating this directory, which is reused by Nova, as demonstrated using /tmp/keystone-signing-nova on Fedora.

Other sources

Originally reported by Grant Murphy (gmurphy):

The signing directory is used to store the signing certificates and the default location for this directory is:

signingdir = /tmp/keystone-signing-nova

In the file:

keystone/middleware/authtoken.py

During the initialization of the AuthMiddleware the following operations are made for the signing directory:

IF the directory exists but cannot be written to a configuration error is raised. ELSE IF the directory doesn't exist, create it. NEXT chmod permisions(stat.SIRWXU) to the signingdirectory

AFAICT The signing certificates used in validation will only be fetched from the keystone if the cmsverify action raises an exception because the certificate file is missing from the signing directory.

This means that if an attacker populated the /tmp/keystone-signing-nova with the appropriate files for signautre verification they could potentially issue forged tokens which would be validated by the middleware. As: - The directory location deterministic. (default for glance, nova) - If the directory already exists it is reused

Red Hat

Affected Software

10 affected componentsFixes available
pip/python-keystoneclient<0.2.4
0.2.4
Openstack Compute=2013.1
Openstack Compute=2013.1.1
Openstack Compute=2013.1.2
Openstack Compute=2013.1.3
Openstack folsom
Openstack Grizzly=2013.1
Openstack Havana=havana-1
Openstack Havana=havana-2
Openstack Havana=havana-3

Event History

Apr 30, 2013
Data Sourced
via Red Hat·08:11 PM
DescriptionSeverityAffected Software
Dec 27, 2013
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
May 17, 2022
Advisory Published
04:44 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-2030?

CVE-2013-2030 has a medium severity rating due to its potential for local users to spoof servers.

2

How do I fix CVE-2013-2030?

To fix CVE-2013-2030, ensure the application uses a secure and unique temporary directory for storing signing certificates.

3

Which versions of OpenStack are affected by CVE-2013-2030?

CVE-2013-2030 affects OpenStack Nova versions Folsom, Grizzly, and Havana prior to their respective fixes.

4

Can CVE-2013-2030 be exploited remotely?

No, CVE-2013-2030 can only be exploited by local users with access to the filesystem.

5

What is the impact of CVE-2013-2030?

The impact of CVE-2013-2030 allows local users to spoof server responses by pre-creating an insecure temporary directory.

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