First published: Tue May 30 2006(Updated: )
Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via a long filename. NOTE: tiffsplit is not setuid. If there is not a common scenario under which tiffsplit is called with attacker-controlled command line arguments, then perhaps this issue should not be included in CVE.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
libtiff | =3.6.1 | |
libtiff | =3.8.0 | |
libtiff | =3.8.1 | |
libtiff | =3.4 | |
libtiff | =3.5.7 | |
libtiff | =3.7.0 | |
libtiff | =3.6.0 | |
libtiff | =3.5.3 | |
libtiff | =3.7.1 | |
libtiff | =3.5.4 | |
libtiff | =3.5.2 | |
libtiff | =3.5.5 | |
libtiff | =3.5.1 | |
libtiff | =3.5.6 | |
libtiff | <=3.8.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-2656 is classified as a moderate severity vulnerability due to the potential for arbitrary code execution from a stack-based buffer overflow.
To remediate CVE-2006-2656, upgrade libtiff to version 3.8.3 or later to ensure the buffer overflow vulnerability is addressed.
CVE-2006-2656 affects libtiff versions 3.8.2 and earlier, including versions 3.6.1, 3.8.0, 3.8.1, and earlier.
Exploiting CVE-2006-2656 may allow an attacker to execute arbitrary code on the affected system through specially crafted long filenames.
While tiffsplit is not setuid, using it in an environment that sanitizes or restricts user input can mitigate the risk associated with CVE-2006-2656.