# CVE-2015-5154: Memory corruption in n/a

> Local guest users can execute arbitrary code on the host via heap overflow in QEMU's IDE subsystem when CDROM is enabled.

- **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:** 12 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-5154, GHSA-j9wc-jv66-352g, SUSE-SU-2015:1409-1, SUSE-SU-2015:1455-1, SUSE-SU-2015:1472-1, UBUNTU-CVE-2015-5154

## What is CVE-2015-5154?

CVE-2015-5154 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 12 Aug 2015. 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 IDE subsystem in QEMU, as used in Xen 4.5.x and earlier, when the container has a CDROM drive enabled, allows local guest users to execute arbitrary code on the host via unspecified ATAPI commands.

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

## Which versions are affected by CVE-2015-5154?

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kvm` | SUSE:Linux Enterprise Desktop 11 SP3 | All versions | 1.4.2-0.22.34.3 |
| `kvm` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 1.4.2-32.1 |
| `kvm` | SUSE:Linux Enterprise Server 11 SP1-LTSS | All versions | 0.12.5-1.30.2 |
| `kvm` | SUSE:Linux Enterprise Server 11 SP1-TERADATA | All versions | 0.12.5-1.30.2 |
| `kvm` | SUSE:Linux Enterprise Server 11 SP3 | All versions | 1.4.2-0.22.34.3 |
| `kvm` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 1.4.2-0.22.34.3 |
| `kvm` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.4.2-32.1 |
| `kvm` | SUSE:Linux Enterprise Server for SAP Applications 11 SP3 | All versions | 1.4.2-0.22.34.3 |
| `kvm` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.4.2-32.1 |

Products: Fedoraproject Fedora, Qemu Qemu, Suse Linux Enterprise Debuginfo, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server, Suse Linux Enterprise Software Development Kit, Suse Suse Linux Enterprise Server, Xen Xen.

## How do I fix CVE-2015-5154?

Apply the vendor's patch.

## Is CVE-2015-5154 being exploited?

There is no known exploitation of CVE-2015-5154 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5154 and fix it if it is affected.

What it is: CVE-2015-5154 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 12 Aug 2015. 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-2015-5154 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2015-5154/ (Markdown: https://insights.sbomify.com/CVE-2015-5154/index.md)
```

## Sources

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

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