# CVE-2007-2893: Memory corruption in n/a

> Local guest users can exploit a heap overflow in the Bochs NE2000 emulation to execute arbitrary code and gain privileges on the host system.

- **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:** 30 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2893, DSA-1351-1, GHSA-4f58-4q55-p757

## What is CVE-2007-2893?

CVE-2007-2893 is a high-severity memory corruption vulnerability in n/a, published on 30 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based buffer overflow in the bx_ne2k_c::rx_frame function in iodev/ne2k.cc in the emulated NE2000 device in Bochs 2.3 allows local users of the guest operating system to write to arbitrary memory locations and gain privileges on the host operating system via vectors that cause TXCNT register values to exceed the device memory size, aka "RX Frame heap overflow."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2007-2893?

It affects 1 product.


Products: Bochs Project Bochs.

## How do I fix CVE-2007-2893?

Upgrade to a fixed version.

## Is CVE-2007-2893 being exploited?

There is no known exploitation of CVE-2007-2893 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-2004-2372](https://insights.sbomify.com/CVE-2004-2372/): 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-2007-2893 and fix it if it is affected.

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

## Sources

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

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