# CVE-2014-0143: Integer overflow in n/a

> Local users can cause a denial of service via crafted disk images triggering integer overflows in QEMU block drivers.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0143, GHSA-p7h7-ff68-wgx2

## What is CVE-2014-0143?

CVE-2014-0143 is a high-severity vulnerability in Qemu Qemu, published on 10 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple integer overflows in the block drivers in QEMU, possibly before 2.0.0, allow local users to cause a denial of service (crash) via a crafted catalog size in (1) the parallels_open function in block/parallels.c or (2) bochs_open function in bochs.c, a large L1 table in the (3) qcow2_snapshot_load_tmp in qcow2-snapshot.c or (4) qcow2_grow_l1_table function in qcow2-cluster.c, (5) a large request in the bdrv_check_byte_request function in block.c and other block drivers, (6) crafted cluster indexes in the get_refcount function in qcow2-refcount.c, or (7) a large number of blocks in the cloop_open function in cloop.c, which trigger buffer overflows, memory corruption, large memory allocations and out-of-bounds read and writes.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2014-0143?

It affects 2 products.


Products: Qemu Qemu, Redhat Enterprise Linux.

## How do I fix CVE-2014-0143?

Upgrade to a fixed version.

## Is CVE-2014-0143 being exploited?

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

What it is: CVE-2014-0143 is a high-severity vulnerability in Qemu Qemu, published on 10 Aug 2017. 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-2014-0143 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-2014-0143/ (Markdown: https://insights.sbomify.com/CVE-2014-0143/index.md)
```

## Sources

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

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