# CVE-2004-2372: Memory corruption in n/a

> Local attackers can execute arbitrary code with elevated privileges via a buffer overflow in the Bochs emulator when installed setuid.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2372, GHSA-g3hw-2h8v-79ff

## What is CVE-2004-2372?

CVE-2004-2372 is a high-severity memory corruption vulnerability in n/a, published on 16 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Bochs before 2.1.1, if installed setuid, allows local users to execute arbitrary code via a long HOME environment variable, which is used if the .bochsrc, bochsrc, and bochsrc.txt cannot be found in a known path.  NOTE: some external documents recommend that Bochs be installed setuid root, so this should be treated as a vulnerability.

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

It affects 1 product.


Products: Bochs Project Bochs.

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

Upgrade to a fixed version.

## Is CVE-2004-2372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-25220](https://insights.sbomify.com/CVE-2018-25220/): Bochs 2.6-5 Buffer Overflow Remote Code Execution (critical 9.3)
- [CVE-2007-2893](https://insights.sbomify.com/CVE-2007-2893/): Memory corruption in n/a (high 7.2)
- [CVE-2007-2894](https://insights.sbomify.com/CVE-2007-2894/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2372 is a high-severity memory corruption vulnerability in n/a, published on 16 Aug 2005. 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-2004-2372 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-2004-2372/ (Markdown: https://insights.sbomify.com/CVE-2004-2372/index.md)
```

## Sources

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

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