CVE-2013-2030: Medium severity openstack compute (nova) vulnerability
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
Remediation
Event History
Frequently Asked Questions
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.
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.
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.
Can CVE-2013-2030 be exploited remotely?
No, CVE-2013-2030 can only be exploited by local users with access to the filesystem.
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.