# CVE-2006-2193: Memory corruption in n/a

> A buffer overflow in libtiff allows attackers to execute arbitrary code or cause a crash by tricking a user into opening a malicious TIFF file.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 8 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2193, GHSA-jgfg-vvq8-cfx3

## What is CVE-2006-2193?

CVE-2006-2193 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 8 Jun 2006. 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

Buffer overflow in the t2p_write_pdf_string function in tiff2pdf in libtiff 3.8.2 and earlier allows attackers to cause a denial of service (crash) and possibly execute arbitrary code via a TIFF file with a DocumentName tag that contains UTF-8 characters, which triggers the overflow when a character is sign extended to an integer that produces more digits than expected in an sprintf call.

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

It affects 1 product.


Products: Libtiff Libtiff.

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

Upgrade to a fixed version.

## Is CVE-2006-2193 being exploited?

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

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

## Sources

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

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