# CVE-2006-2024: Denial of service in n/a

> Attackers can cause denial of service in applications using libtiff by providing specially crafted TIFF images that trigger errors in various decoding functions.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2024, GHSA-gcqf-gvjg-mhm8

## What is CVE-2006-2024?

CVE-2006-2024 is a medium-severity denial of service vulnerability in Libtiff Libtiff, published on 25 Apr 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple vulnerabilities in libtiff before 3.8.1 allow context-dependent attackers to cause a denial of service via a TIFF image that triggers errors in (1) the TIFFFetchAnyArray function in (a) tif_dirread.c; (2) certain "codec cleanup methods" in (b) tif_lzw.c, (c) tif_pixarlog.c, and (d) tif_zip.c; (3) and improper restoration of setfield and getfield methods in cleanup functions within (e) tif_jpeg.c, tif_pixarlog.c, (f) tif_fax3.c, and tif_zip.c.

## Which versions are affected by CVE-2006-2024?

It affects 1 product.


Products: Libtiff Libtiff.

## How do I fix CVE-2006-2024?

Upgrade to a fixed version.

## Is CVE-2006-2024 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2024 exists.

Public exploit code:

- LibTiff 3.x - Multiple Denial of Service Vulnerabilities (exploitdb)

## 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-2006-2024 and fix it if it is affected.

What it is: CVE-2006-2024 is a medium-severity denial of service vulnerability in Libtiff Libtiff, published on 25 Apr 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2024 exists.

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-2006-2024/ (Markdown: https://insights.sbomify.com/CVE-2006-2024/index.md)
```

## Sources

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

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