# CVE-2009-3616: Use after free in n/a

> Guest OS users can execute arbitrary code on the host OS via use-after-free flaws in the QEMU VNC server during specific connection states.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-3616, GHSA-vmwq-xc6v-xj4j

## What is CVE-2009-3616?

CVE-2009-3616 is a critical use after free vulnerability in Qemu Qemu, published on 23 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple use-after-free vulnerabilities in vnc.c in the VNC server in QEMU 0.10.6 and earlier might allow guest OS users to execute arbitrary code on the host OS by establishing a connection from a VNC client and then (1) disconnecting during data transfer, (2) sending a message using incorrect integer data types, or (3) using the Fuzzy Screen Mode protocol, related to double free vulnerabilities.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2009-3616?

It affects 3 products.


Products: Qemu Qemu, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2009-3616?

Upgrade to a fixed version.

## Is CVE-2009-3616 being exploited?

There is no known exploitation of CVE-2009-3616 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-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)
- [CVE-2018-20815](https://insights.sbomify.com/CVE-2018-20815/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3616 and fix it if it is affected.

What it is: CVE-2009-3616 is a critical use after free vulnerability in Qemu Qemu, published on 23 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3616 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-2009-3616/ (Markdown: https://insights.sbomify.com/CVE-2009-3616/index.md)
```

## Sources

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

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