# CVE-2013-0335: Openstack nova: vnc proxy can connect to the wrong vm

> Authenticated users can access deleted VMs via VNC token reuse on recycled ports, allowing unauthorized console access.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Mar 2013
- **Updated:** 31 Jul 2026
- **Also known as:** DEBIAN-CVE-2013-0335, GHSA-qfp8-hfqx-c79c, PYSEC-2013-43

## What is CVE-2013-0335?

CVE-2013-0335 is a high-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 22 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Compute (Nova) Grizzly, Folsom (2012.2), and Essex (2012.1) allows remote authenticated users to gain access to a VM in opportunistic circumstances by using the VNC token for a deleted VM that was bound to the same VNC port.

Weakness: CWE-264, CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

3 open source packages ship an affected version, including nova and Nova. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nova` | PyPI | All versions | 12.0.0a0 |
| `nova` | PyPI | All versions | 12.0.0a0 |
| `Nova` | PyPI | All versions | 12.0.0a0 |

Products: Canonical Ubuntu Linux, Openstack Essex, Openstack Folsom, Openstack Grizzly.

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

Upgrade nova to 12.0.0a0 or later.

## Is CVE-2013-0335 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0335 is a high-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 22 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0335 in the wild and no public exploit code.

Affected packages and fixed versions:
- nova (PyPI): affected all versions; fixed in 12.0.0a0
- nova (PyPI): affected all versions; fixed in 12.0.0a0
- Nova (PyPI): affected all versions; fixed in 12.0.0a0

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-0335/ (Markdown: https://insights.sbomify.com/CVE-2013-0335/index.md)
```

## Sources

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

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