CVE-2017-17095 Memory corruption in n/a

High 8.8 Published 2 Dec 2017 Updated 5 Aug 2024

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.

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

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

Which versions are affected by CVE-2017-17095?

It affects 1 product.

Linux distribution packages (13)

`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 include Libtiff Libtiff.

How do I fix CVE-2017-17095?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

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: 1 Exploit-DB entry.

All Libtiff Libtiff vulnerabilities

Sources

Also known as ALPINE-CVE-2017-17095, ALSA-2025:4658, DEBIAN-CVE-2017-17095, GHSA-v9h2-67w5-wp47, RHSA-2025:4658, RLSA-2025:4658 and 1 more.