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-2013-4231

(gif2tiff): GIF LZW decoder missing datasize value check

Overview

Published
19 Jan 2014
Modified
29 Apr 2026
Medium CVE
0 Registry packages
6 OS packages
4 Linux distributions
Yes Fix available

Description

Multiple buffer overflows in libtiff before 4.0.3 allow remote attackers to cause a denial of service (out-of-bounds write) via a crafted (1) extension block in a GIF image or (2) GIF raster image to tools/gif2tiff.c or (3) a long filename for a TIFF image to tools/rgb2ycbcr.c. NOTE: vectors 1 and 3 are disputed by Red Hat, which states that the input cannot exceed the allocated buffer size.

Source: OX vulnerability database

Severity

5.1 · MEDIUM

CVSS 2.0 base score, scored by redhat.

Access vector
Network
Access complexity
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/Au:N/C:P/I:P/A:P

Weakness: CWE-119

Affected packages · 0

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

Operating systems · 9 fixes

debian 4 releases · 1 package

fixed 4
tiff
debian fixes for CVE-2013-4231
ReleasePackageFixed in
11 tiff 4.0.3-2
12 tiff 4.0.3-2
13 tiff 4.0.3-2
14 tiff 4.0.3-2

echo 1 release · 1 package

fixed 1
tiff
echo fixes for CVE-2013-4231
ReleasePackageFixed in
tiff 4.0.3-2

openSUSE 1 release · 1 package

fixed 1
libtiff-devel
openSUSE fixes for CVE-2013-4231
ReleasePackageFixed inAdvisory
Tumbleweed libtiff-devel +4 4.0.7-1.1 openSUSE-SU-2024:10554-1

root.io debian 3 releases · 1 package

fixed 3
rootio-tiff
root.io debian fixes for CVE-2013-4231
ReleasePackageFixed in
11 rootio-tiff 4.0.3-2
12 rootio-tiff 4.0.3-2
13 rootio-tiff 4.0.3-2

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.