CVE-2017-5563 Memory corruption in n/a

High 8.8 Published Updated

A heap-based buffer over-read in LibTIFF allows attackers to execute arbitrary code or cause denial of service via a crafted BMP image.

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-5563?

CVE-2017-5563 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 23 Jan 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

LibTIFF version 4.0.7 is vulnerable to a heap-based buffer over-read in tif_lzw.c resulting in DoS or code execution via a crafted bmp image to tools/bmp2tiff.

Weakness: CWE-125

Which versions are affected by CVE-2017-5563?

It affects 1 product.

Products include Libtiff Libtiff.

How do I fix CVE-2017-5563?

Upgrade to a fixed version.

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

Is CVE-2017-5563 being exploited?

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

All Libtiff Libtiff vulnerabilities

Sources

Also known as AZL-45150, DEBIAN-CVE-2017-5563, ECHO-9a38-e230-2936, GHSA-qvg6-9fpw-3vw9, UBUNTU-CVE-2017-5563.

Is CVE-2017-5563 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free