# CVE-2019-17546: Integer overflow in n/a

> An integer overflow in LibTIFF allows attackers to cause a heap-based buffer overflow via a crafted RGBA image, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2019
- **Updated:** 20 Dec 2024
- **Also known as:** ALSA-2020:4634, AZL-44190, DEBIAN-CVE-2019-17546, DLA-2147-1, GHSA-24m4-fmx6-c2q6, JLSEC-2025-254, MGASA-2019-0366, RHSA-2020:4634, RLSA-2020:4634, UBUNTU-CVE-2019-17546

## What is CVE-2019-17546?

CVE-2019-17546 is a high-severity vulnerability in Libtiff Libtiff, published on 14 Oct 2019. 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

tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer overflow via a crafted RGBA image, related to a "Negative-size-param" condition.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2019-17546?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libtiff-tools` | AlmaLinux:8 | All versions | 4.0.9-18.el8 |
| `libtiff` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-18.el8 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-18.el8 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-18.el8 |
| `libtiff-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-18.el8 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-18.el8 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-18.el8 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-18.el8 |
| `libtiff-tools` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-18.el8 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-18.el8 |
| `libtiff` | Rocky Linux:8 | All versions | 0:4.0.9-18.el8 |

Products: Libtiff Libtiff, Osgeo Gdal.

## How do I fix CVE-2019-17546?

Apply the vendor's patch.

## Is CVE-2019-17546 being exploited?

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

What it is: CVE-2019-17546 is a high-severity vulnerability in Libtiff Libtiff, published on 14 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-17546 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-2019-17546/ (Markdown: https://insights.sbomify.com/CVE-2019-17546/index.md)
```

## Sources

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

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