# CVE-2017-17095: Memory corruption in n/a

> A heap-based buffer overflow in LibTIFF allows remote attackers to cause a denial of service or potentially execute code via a crafted TIFF file.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 2 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-17095, ALSA-2025:4658, DEBIAN-CVE-2017-17095, GHSA-v9h2-67w5-wp47, RHSA-2025:4658, RLSA-2025:4658, UBUNTU-CVE-2017-17095

## What is CVE-2017-17095?

CVE-2017-17095 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 2 Dec 2017. 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

tools/pal2rgb.c in pal2rgb in LibTIFF 4.0.9 allows remote attackers to cause a denial of service (TIFFSetupStrips heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted TIFF file.

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

## Which versions are affected by CVE-2017-17095?

It affects 1 product.


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

Products: Libtiff Libtiff.

## How do I fix CVE-2017-17095?

Apply the vendor's patch.

## Is CVE-2017-17095 being exploited?

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

Public exploit code:

- LibTIFF pal2rgb 4.0.9 - Heap Buffer Overflow (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-2017-17095 and fix it if it is affected.

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

## Sources

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

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