# CVE-2008-2004: Information disclosure in n/a

> Local guest users can read arbitrary host files by manipulating disk image headers, impacting QEMU virtualization environments.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/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:** 12 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2004, GHSA-rx7x-x8p7-jfcr

## What is CVE-2008-2004?

CVE-2008-2004 is a medium-severity vulnerability in Qemu Qemu, published on 12 May 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The drive_init function in QEMU 0.9.1 determines the format of a raw disk image based on the header, which allows local guest users to read arbitrary files on the host by modifying the header to identify a different format, which is used when the guest is restarted.

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

## Which versions are affected by CVE-2008-2004?

It affects 1 product.


Products: Qemu Qemu.

## How do I fix CVE-2008-2004?

Apply the vendor's patch.

## Is CVE-2008-2004 being exploited?

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

## Other vulnerabilities in Qemu Qemu

- [CVE-2022-36648](https://insights.sbomify.com/CVE-2022-36648/): Null dereference in n/a (critical 10.0)
- [CVE-2015-8556](https://insights.sbomify.com/CVE-2015-8556/): Race condition in n/a (critical 10.0)
- [CVE-2009-3616](https://insights.sbomify.com/CVE-2009-3616/): Use after free in n/a (critical 9.9)
- [CVE-2019-12928](https://insights.sbomify.com/CVE-2019-12928/): Command injection in n/a (critical 9.8)
- [CVE-2019-12929](https://insights.sbomify.com/CVE-2019-12929/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2004 and fix it if it is affected.

What it is: CVE-2008-2004 is a medium-severity vulnerability in Qemu Qemu, published on 12 May 2008. 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-2008-2004 in the wild and no public exploit code.

Affected product: Qemu Qemu. 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-2008-2004/ (Markdown: https://insights.sbomify.com/CVE-2008-2004/index.md)
```

## Sources

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

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