# CVE-2013-0208: Missing authorization in n/a

> Authenticated users can access other users' volumes by manipulating volume IDs, leading to unauthorized data access and modification.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 13 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0208, GHSA-rr64-vh7q-pgrf, RHSA-2013:0208

## What is CVE-2013-0208?

CVE-2013-0208 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 13 Feb 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The boot-from-volume feature in OpenStack Compute (Nova) Folsom and Essex, when using nova-volumes, allows remote authenticated users to boot from other users' volumes via a volume id in the block_device_mapping parameter.

Weakness: CWE-264

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-nova` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-api` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-cert` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-common` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-compute` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-console` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-doc` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-network` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-objectstore` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-scheduler` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `openstack-nova-volume` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |
| `python-nova` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.2-8.el6ost |

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

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

Apply the vendor's patch.

## Is CVE-2013-0208 being exploited?

There is no known exploitation of CVE-2013-0208 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-0208 and fix it if it is affected.

What it is: CVE-2013-0208 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 13 Feb 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-0208 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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