# CVE-2013-4537: Code injection in n/a

> Remote attackers can execute arbitrary code in QEMU by providing a crafted savevm image with a malicious arglen value.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4537, GHSA-mhh8-cmv6-m67q, UBUNTU-CVE-2013-4537

## What is CVE-2013-4537?

CVE-2013-4537 is a high-severity code injection vulnerability in Qemu Qemu, published on 4 Nov 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ssi_sd_transfer function in hw/sd/ssi-sd.c in QEMU before 1.7.2 allows remote attackers to execute arbitrary code via a crafted arglen value in a savevm image.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Qemu Qemu.

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

Upgrade to a fixed version.

## Is CVE-2013-4537 being exploited?

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

What it is: CVE-2013-4537 is a high-severity code injection vulnerability in Qemu Qemu, published on 4 Nov 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-4537 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-4537/ (Markdown: https://insights.sbomify.com/CVE-2013-4537/index.md)
```

## Sources

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

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