First published: Mon Aug 12 2013(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
tiff | <=4.0.2 | |
tiff | =4.0 | |
tiff | =4.0-alpha | |
tiff | =4.0-beta1 | |
tiff | =4.0-beta2 | |
tiff | =4.0-beta3 | |
tiff | =4.0-beta4 | |
tiff | =4.0-beta5 | |
tiff | =4.0-beta6 | |
tiff | =4.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4231 has a moderate severity, as it can lead to denial of service through out-of-bounds writes.
To fix CVE-2013-4231, update libtiff to version 4.0.3 or later.
CVE-2013-4231 allows remote attackers to exploit buffer overflows in libtiff through crafted GIF images.
CVE-2013-4231 affects libtiff versions before 4.0.3, including all releases from 4.0.2 and earlier.
Yes, the tools gif2tiff.c and rgb2ycbcr.c are specifically vulnerable to CVE-2013-4231.