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

> Remote attackers can cause denial of service via out-of-bounds write in LibTIFF's rgb2ycbcr tool using a specific command-line option.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 3 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2016-3624, DEBIAN-CVE-2016-3624, GHSA-g6q5-rqfh-3jr6, UBUNTU-CVE-2016-3624

## What is CVE-2016-3624?

CVE-2016-3624 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 3 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The cvtClump function in the rgb2ycbcr tool in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (out-of-bounds write) by setting the "-v" option to -1.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Libtiff Libtiff.

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

Upgrade to a fixed version.

## Is CVE-2016-3624 being exploited?

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

What it is: CVE-2016-3624 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 3 Oct 2016. 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-3624 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-3624/ (Markdown: https://insights.sbomify.com/CVE-2016-3624/index.md)
```

## Sources

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

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