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

> Local users in a Windows guest can exploit a buffer overflow in QEMU to execute arbitrary code or escalate privileges.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6p9f-vrqh-5hfv

## What is CVE-2007-6227?

CVE-2007-6227 is a high-severity memory corruption vulnerability in Qemu Qemu, published on 4 Dec 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

QEMU 0.9.0 allows local users of a Windows XP SP2 guest operating system to overwrite the TranslationBlock (code_gen_buffer) buffer, and probably have unspecified other impacts related to an "overflow," via certain Windows executable programs, as demonstrated by qemu-dos.com.

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

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

It affects 1 product.


Products: Qemu Qemu.

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

No fix has been published for CVE-2007-6227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-6227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6227 exists.

Public exploit code:

- QEMU 0.9 - Translation Block Local Denial of Service (exploitdb)

## 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-2007-6227 and fix it if it is affected.

What it is: CVE-2007-6227 is a high-severity memory corruption vulnerability in Qemu Qemu, published on 4 Dec 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6227 exists.

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-2007-6227/ (Markdown: https://insights.sbomify.com/CVE-2007-6227/index.md)
```

## Sources

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

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