cve.bz

CVE-2017-5225 libtiff libtiff: Heap-based Buffer Overflow

8.8 highExploit referenceEPSS 4.4%Fix available

High (8.8) in libtiff libtiff. EPSS 4.4% estimated probability of exploitation activity in the next 30 days.

On this page
LibTIFF version 4.0.7 is vulnerable to a heap buffer overflow in the tools/tiffcp resulting in DoS or code execution via a crafted BitsPerSample value.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
4.4% (unchanged from 4.4% a week ago; 4.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-10-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-5225 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5225?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5225?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-5225 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
libtiff:libtiff4.0.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian7tiff4.0.2-6+deb7u9DLA-795-1
Debian8tiff4.0.3-12.3+deb8u3DSA-3844-1
Debian12, 13, 14tiff4.0.7-5DEBIAN-CVE-2017-5225
Ubuntu14.04:LTStiff4.0.3-7ubuntu0.6UBUNTU-CVE-2017-5225 USN-3212-1
Ubuntu16.04:LTStiff4.0.6-1ubuntu0.1UBUNTU-CVE-2017-5225 USN-3212-1
SUSELinux Enterprise Desktop 12 SP1, Linux Enterprise Desktop 12 SP2, Linux Enterprise Server 12 SP1 and 6 moretiff4.0.7-40.1SUSE-SU-2017:0453-1
SUSELinux Enterprise Server 11 SP4, Linux Enterprise Server for SAP Applications 11 SP4, Linux Enterprise Software Development Kit 11 SP4tiff3.8.2-141.169.9.1SUSE-SU-2018:1835-1
openSUSETumbleweedtiff4.3.0-1.3openSUSE-SU-2024:11461-1
Alpinev3.2, v3.3, v3.4 and 20 moretiff4.0.7-r1ALPINE-CVE-2017-5225

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This is a heap-based buffer overflow in the tiffcp utility of libtiff. A specially-crafted image when processed via the tiffcp binary, could cause it to crash or execute arbitrary code with the permissions of the user running the utility.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 5libtiffWill not fix
Red Hat Enterprise Linux 6libtiffWill not fix
Red Hat Enterprise Linux 7compat-libtiff3Will not fix
Red Hat Enterprise Linux 7libtiffWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-5225.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON