# CVE-2010-2239: Information disclosure in n/a

> Guest OS users can read arbitrary host files due to missing backing-store format validation in libvirt image creation.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:S/C:C/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:** 19 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2239, GHSA-9w2j-rv9v-ph7h

## What is CVE-2010-2239?

CVE-2010-2239 is a medium-severity vulnerability in n/a, published on 19 Aug 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red Hat libvirt, possibly 0.6.0 through 0.8.2, creates new images without setting the user-defined backing-store format, which allows guest OS users to read arbitrary files on the host OS via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2010-2239?

It affects 1 product.


Products: Libvirt Libvirt.

## How do I fix CVE-2010-2239?

Apply the vendor's patch.

## Is CVE-2010-2239 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5086](https://insights.sbomify.com/CVE-2008-5086/): Missing authorization in n/a (high 7.2)
- [CVE-2015-5160](https://insights.sbomify.com/CVE-2015-5160/): Information disclosure in n/a (medium 5.5)
- [CVE-2014-3657](https://insights.sbomify.com/CVE-2014-3657/): Denial of service in n/a (medium 5.0)
- [CVE-2010-2237](https://insights.sbomify.com/CVE-2010-2237/): Information disclosure in n/a (medium 4.4)
- [CVE-2010-2238](https://insights.sbomify.com/CVE-2010-2238/): Path traversal in n/a (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2239 and fix it if it is affected.

What it is: CVE-2010-2239 is a medium-severity vulnerability in n/a, published on 19 Aug 2010. 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-2010-2239 in the wild and no public exploit code.

Affected product: n/a. 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-2010-2239/ (Markdown: https://insights.sbomify.com/CVE-2010-2239/index.md)
```

## Sources

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

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