Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
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-13726

libtiff: Reachable assertion abort in the function TIFFWriteDirectorySec()

Overview

Published
29 Aug 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
8 OS packages
5 Linux distributions
Yes Fix available

Description

There is a reachable assertion abort in the function TIFFWriteDirectorySec() in LibTIFF 4.0.8, related to tif_dirwrite.c and a SubIFD tag. A crafted input will lead to a remote denial of service attack.

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-617

Affected packages · 0

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

Operating systems · 11 fixes

Red Hat 1 release · 1 package

wont fix 1
compat-libtiff3
Red Hat fixes for CVE-2017-13726
ReleasePackageFixed in
7 compat-libtiff3 +4 wont fix

debian 5 releases · 1 package

fixed 5
tiff
debian fixes for CVE-2017-13726
ReleasePackageFixed in
11 tiff 4.0.8-5
12 tiff 4.0.8-5
13 tiff 4.0.8-5
14 tiff 4.0.8-5
9 tiff 4.0.8-2+deb9u2

echo 1 release · 1 package

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

root.io debian 3 releases · 1 package

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

seal Red Hat 1 release · 1 package

fixed 1
libtiff
seal Red Hat fixes for CVE-2017-13726
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.