First published: Wed Oct 17 2012(Updated: )
A stack-based buffer overflow was found in the way libtiff handled DOTRANGE tags. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. This issue is fixed in libtiff-4.0.2
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
tiff | <=4.0.1 | |
tiff | =3.4 | |
tiff | =3.4-beta18 | |
tiff | =3.4-beta24 | |
tiff | =3.4-beta28 | |
tiff | =3.4-beta29 | |
tiff | =3.4-beta31 | |
tiff | =3.4-beta32 | |
tiff | =3.4-beta34 | |
tiff | =3.4-beta35 | |
tiff | =3.4-beta36 | |
tiff | =3.4-beta37 | |
tiff | =3.5.1 | |
tiff | =3.5.2 | |
tiff | =3.5.3 | |
tiff | =3.5.4 | |
tiff | =3.5.5 | |
tiff | =3.5.6 | |
tiff | =3.5.6-beta | |
tiff | =3.5.7 | |
tiff | =3.5.7-alpha | |
tiff | =3.5.7-alpha2 | |
tiff | =3.5.7-alpha3 | |
tiff | =3.5.7-alpha4 | |
tiff | =3.5.7-beta | |
tiff | =3.6.0 | |
tiff | =3.6.0-beta | |
tiff | =3.6.0-beta2 | |
tiff | =3.6.1 | |
tiff | =3.7.0 | |
tiff | =3.7.0-alpha | |
tiff | =3.7.0-beta | |
tiff | =3.7.0-beta2 | |
tiff | =3.7.1 | |
tiff | =3.7.2 | |
tiff | =3.7.3 | |
tiff | =3.7.4 | |
tiff | =3.8.0 | |
tiff | =3.8.1 | |
tiff | =3.8.2 | |
tiff | =3.9 | |
tiff | =3.9.0 | |
tiff | =3.9.0-beta | |
tiff | =3.9.1 | |
tiff | =3.9.2 | |
tiff | =3.9.2-5.2.1 | |
tiff | =3.9.3 | |
tiff | =3.9.4 | |
tiff | =3.9.5 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-5581 has been categorized as a high severity vulnerability due to its potential for exploitation leading to application crashes or arbitrary code execution.
To fix CVE-2012-5581, update your libtiff library to version 4.0.2 or later, which addresses this buffer overflow vulnerability.
CVE-2012-5581 affects multiple versions of libtiff, specifically versions prior to 4.0.2, including various 3.x and 4.x beta releases.
CVE-2012-5581 can facilitate a remotely executed attack where a specially-crafted TIFF file causes an application using libtiff to crash or execute arbitrary code.
Any application that uses the vulnerable versions of the libtiff library for image processing tasks could be impacted by CVE-2012-5581.