Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-9815

libtiff: Memory leak in the TIFFReadDirEntryLong8Array function

Overview

Published
22 Jun 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
7 OS packages
5 Linux distributions
Yes Fix available

Description

In LibTIFF 4.0.7, the TIFFReadDirEntryLong8Array function in libtiff/tif_dirread.c mishandles a malloc operation, which allows attackers to cause a denial of service (memory leak within the function _TIFFmalloc in tif_unix.c) via a crafted file.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-772

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

Red Hat 1 release · 1 package

wont fix 1
libtiff
Red Hat fixes for CVE-2017-9815
ReleasePackageFixed in
7 libtiff +3 wont fix

debian 4 releases · 1 package

fixed 4
tiff
debian fixes for CVE-2017-9815
ReleasePackageFixed in
11 tiff 4.0.8-1
12 tiff 4.0.8-1
13 tiff 4.0.8-1
14 tiff 4.0.8-1

echo 1 release · 1 package

fixed 1
tiff
echo fixes for CVE-2017-9815
ReleasePackageFixed in
tiff 4.0.8-1

root.io debian 3 releases · 1 package

fixed 3
rootio-tiff
root.io debian fixes for CVE-2017-9815
ReleasePackageFixed in
11 rootio-tiff 4.0.8-1
12 rootio-tiff 4.0.8-1
13 rootio-tiff 4.0.8-1

seal Red Hat 1 release · 1 package

fixed 1
libtiff
seal Red Hat fixes for CVE-2017-9815
ReleasePackageFixed in
7 libtiff +1 4.0.3-35.el7+sp8

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.