# CVE-2013-4183: OpenStack Cinder LVMVolumeDriver does not zero deleted snapshots

> Local users can obtain sensitive information from deleted snapshots due to improper data clearing in OpenStack Cinder.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 16 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4183, GHSA-q3rw-wcj6-8cjf, PYSEC-2013-35

## What is CVE-2013-4183?

CVE-2013-4183 is a low-severity vulnerability in n/a, published on 16 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The clear_volume function in LVMVolumeDriver driver in OpenStack Cinder 2013.1.1 through 2013.1.2 does not properly clear data when deleting a snapshot, which allows local users to obtain sensitive information via unspecified vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including cinder. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cinder` | PyPI | All versions | 7.0.0a0 |
| `cinder` | PyPI | All versions | 7.0.0a0 |
| `cinder` | PyPI | All versions | 7.0.0a0 |

Products: Openstack Cinder.

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

Upgrade cinder to 7.0.0a0 or later.

## Is CVE-2013-4183 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5162](https://insights.sbomify.com/CVE-2015-5162/): OpenStack Cinder, Glance, and Nova contain Uncontrolled Resource Consumption (high 7.5)
- [CVE-2024-32498](https://insights.sbomify.com/CVE-2024-32498/): OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access (medium 6.5)
- [CVE-2017-15139](https://insights.sbomify.com/CVE-2017-15139/): Information disclosure in openstack-cinder (medium 5.1)
- [CVE-2014-3641](https://insights.sbomify.com/CVE-2014-3641/): OpenStack Cinder Exposure of Sensitive Information to an Unauthorized Actor vulnerability (medium 4.0)
- [CVE-2014-7231](https://insights.sbomify.com/CVE-2014-7231/): OpenStack Oslo utility sensitive information exposure via log files (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4183 is a low-severity vulnerability in n/a, published on 16 Sep 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-4183 in the wild and no public exploit code.

Affected packages and fixed versions:
- cinder (PyPI): affected all versions; fixed in 7.0.0a0
- cinder (PyPI): affected all versions; fixed in 7.0.0a0
- cinder (PyPI): affected all versions; fixed in 7.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-4183/ (Markdown: https://insights.sbomify.com/CVE-2013-4183/index.md)
```

## Sources

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

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