# CVE-2016-10722: Memory corruption in n/a

> Heap-based buffer overflow in Partclone allows arbitrary code execution via a crafted FAT superblock, affecting users running the disk cloning tool.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2016-10722, GHSA-x4mv-vp4m-f5w6, UBUNTU-CVE-2016-10722

## What is CVE-2016-10722?

CVE-2016-10722 is a critical memory corruption vulnerability in n/a, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

partclone.fat in Partclone before 0.2.88 is prone to a heap-based buffer overflow vulnerability due to insufficient validation of the FAT superblock, related to the mark_reserved_sectors function. An attacker may be able to execute arbitrary code in the context of the user running the affected application.

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

## Which versions are affected by CVE-2016-10722?

It affects 1 product.


Products: Partclone Project Partclone.

## How do I fix CVE-2016-10722?

Upgrade to a fixed version.

## Is CVE-2016-10722 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6596](https://insights.sbomify.com/CVE-2017-6596/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10722 and fix it if it is affected.

What it is: CVE-2016-10722 is a critical memory corruption vulnerability in n/a, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10722 in the wild and no public exploit code.

Affected product: n/a. 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-2016-10722/ (Markdown: https://insights.sbomify.com/CVE-2016-10722/index.md)
```

## Sources

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

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