# CVE-2013-2030: OpenStack Nova uses insecure keystone middleware tmpdir by default

> Local attackers can spoof servers by pre-creating an insecure temporary directory used by OpenStack Nova for signing certificates.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pxxv-rv32-2qgv, PYSEC-2026-911

## What is CVE-2013-2030?

CVE-2013-2030 is a low-severity path traversal vulnerability in n/a, published on 27 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

keystone/middleware/auth_token.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.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2030?

3 open source packages ship an affected version, including python-keystoneclient. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-keystoneclient` | PyPI | All versions | 0.2.4 |
| `python-keystoneclient` | PyPI | All versions | 0.2.4 |
| `python-keystoneclient` | PyPI | All versions | 0.2.4 |

Products: Openstack Compute, Openstack Folsom, Openstack Grizzly, Openstack Havana.

## How do I fix CVE-2013-2030?

Upgrade python-keystoneclient to 0.2.4 or later.

## Is CVE-2013-2030 being exploited?

There is no known exploitation of CVE-2013-2030 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-7130](https://insights.sbomify.com/CVE-2013-7130/): OpenStack Nova Live migration can leak root disk into ephemeral storage (high 7.1)
- [CVE-2014-0167](https://insights.sbomify.com/CVE-2014-0167/): OpenStack Compute (Nova) allows remote authenticated users to gain privileges via API requests (medium 6.0)
- [CVE-2015-2687](https://insights.sbomify.com/CVE-2015-2687/): OpenStack Compute (Nova) Improper Access Control (medium 4.7)
- [CVE-2013-4179](https://insights.sbomify.com/CVE-2013-4179/): OpenStack Compute (Nova) vulnerable to denial of service via XML Entity Expansion attack (medium 4.3)
- [CVE-2012-2654](https://insights.sbomify.com/CVE-2012-2654/): OpenStack Compute (Nova) Improper Input Validation (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2030 and fix it if it is affected.

What it is: CVE-2013-2030 is a low-severity path traversal vulnerability in n/a, published on 27 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2030 in the wild and no public exploit code.

Affected packages and fixed versions:
- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4
- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4
- python-keystoneclient (PyPI): affected all versions; fixed in 0.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2030/ (Markdown: https://insights.sbomify.com/CVE-2013-2030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2030
- OSV: https://osv.dev/vulnerability/CVE-2013-2030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2030/
Summaries are generated and may contain mistakes; the official description above is the record.