# CVE-2013-4377: Use after free in n/a

> Local users can crash the Qemu daemon by hot-unplugging a virtio device, causing a denial of service.

- **Severity:** Low 2.3 (`AV:A/AC:M/Au:S/C:N/I:N/A:P`)
- **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:** 11 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4377, GHSA-rr2r-jfm5-mmxg, MGASA-2014-0060

## What is CVE-2013-4377?

CVE-2013-4377 is a low-severity use after free vulnerability in Qemu Qemu, published on 11 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use-after-free vulnerability in the virtio-pci implementation in Qemu 1.4.0 through 1.6.0 allows local users to cause a denial of service (daemon crash) by "hot-unplugging" a virtio device.

Weakness: CWE-399

## Which versions are affected by CVE-2013-4377?

It affects 1 product.


Products: Qemu Qemu.

## How do I fix CVE-2013-4377?

Upgrade to a fixed version.

## Is CVE-2013-4377 being exploited?

There is no known exploitation of CVE-2013-4377 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-2013-4377 and fix it if it is affected.

What it is: CVE-2013-4377 is a low-severity use after free vulnerability in Qemu Qemu, published on 11 Oct 2013. 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-2013-4377 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-2013-4377/ (Markdown: https://insights.sbomify.com/CVE-2013-4377/index.md)
```

## Sources

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

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