# CVE-2016-5652: Memory corruption in LibTiff

> A heap-based buffer overflow in LibTIFF's TIFF2PDF tool allows remote code execution via crafted TIFF files.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2016-5652, DEBIAN-CVE-2016-5652, GHSA-6mjw-r7c8-wvv4, UBUNTU-CVE-2016-5652

## What is CVE-2016-5652?

CVE-2016-5652 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 6 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An exploitable heap-based buffer overflow exists in the handling of TIFF images in LibTIFF's TIFF2PDF tool. A crafted TIFF document can lead to a heap-based buffer overflow resulting in remote code execution. Vulnerability can be triggered via a saved TIFF file delivered by other means.

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

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

It affects 1 product.


Products: Libtiff Libtiff.

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

Apply the vendor's patch.

## Is CVE-2016-5652 being exploited?

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

## Other vulnerabilities in Libtiff Libtiff

- [CVE-2004-1308](https://insights.sbomify.com/CVE-2004-1308/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0929](https://insights.sbomify.com/CVE-2004-0929/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-61144](https://insights.sbomify.com/CVE-2025-61144/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9533](https://insights.sbomify.com/CVE-2016-9533/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9534](https://insights.sbomify.com/CVE-2016-9534/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5652 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 6 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-5652 in the wild and no public exploit code.

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

## Sources

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

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