This update of libtiff is the result of a source-code audit done by Tavis Ormandy. It fixes various bugs that can lead to denial-of-service conditions as well as to remote code execution while parsing a tiff image. (CVE-2006-3459, CVE-2006-3460, CVE-2006-3461, CVE-2006-3462, CVE-2006-3463, CVE-2006-3464, CVE-2006-3465)

Please restart your applications.

The remote NewStart CGSL host, running version MAIN 6.02, has libtiff packages installed that are affected by multiple vulnerabilities:

  - Buffer overflow in the t2p_write_pdf_string function in tiff2pdf in libtiff 3.8.2 and earlier allows     attackers to cause a denial of service (crash) and possibly execute arbitrary code via a TIFF file with a     DocumentName tag that contains UTF-8 characters, which triggers the overflow when a character is sign     extended to an integer that produces more digits than expected in an sprintf call. (CVE-2006-2193)

  - Heap-based buffer overflow in the JPEG decoder in the TIFF library (libtiff) before 3.8.2 allows context-     dependent attackers to cause a denial of service and possibly execute arbitrary code via an encoded JPEG     stream that is longer than the scan line size (TiffScanLineSize). (CVE-2006-3460)

  - Heap-based buffer overflow in the PixarLog decoder in the TIFF library (libtiff) before 3.8.2 might allow     context-dependent attackers to execute arbitrary code via unknown vectors. (CVE-2006-3461)

  - Heap-based buffer overflow in the NeXT RLE decoder in the TIFF library (libtiff) before 3.8.2 might allow     context-dependent attackers to execute arbitrary code via unknown vectors involving decoding large RLE     images. (CVE-2006-3462)

  - The EstimateStripByteCounts function in TIFF library (libtiff) before 3.8.2 uses a 16-bit unsigned short     when iterating over an unsigned 32-bit value, which allows context-dependent attackers to cause a denial     of service via a large td_nstrips value, which triggers an infinite loop. (CVE-2006-3463)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Tavis Ormandy discovered that the TIFF library did not sufficiently check handled images for validity. By tricking an user or an automated system into processing a specially crafted TIFF image, an attacker could exploit these weaknesses to execute arbitrary code with the target application's privileges.

This library is used in many client and server applications, thus you should reboot your computer after the upgrade to ensure that all running programs use the new version of the library.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-200608-07 (libTIFF: Multiple vulnerabilities)

    Tavis Ormandy of the Google Security Team discovered several heap and     stack-based buffer overflows and other flaws in libTIFF. The affected parts     include the TIFFFetchShortPair(), TIFFScanLineSize() and     EstimateStripByteCounts() functions, and the PixarLog and NeXT RLE     decoders.
  Impact :

    A remote attacker could entice a user to open a specially crafted TIFF     file, resulting in the possible execution of arbitrary code.
  Workaround :

    There is no known workaround at this time.

Updated libtiff packages that fix several security flaws are now available for Red Hat Enterprise Linux.

This update has been rated as having important security impact by the Red Hat Security Response Team.

The libtiff package contains a library of functions for manipulating TIFF (Tagged Image File Format) files.

Tavis Ormandy of Google discovered a number of flaws in libtiff during a security audit. An attacker could create a carefully crafted TIFF file in such a way that it was possible to cause an application linked with libtiff to crash or possibly execute arbitrary code.
(CVE-2006-3459, CVE-2006-3460, CVE-2006-3461, CVE-2006-3462, CVE-2006-3463, CVE-2006-3464, CVE-2006-3465)

All users are advised to upgrade to these updated packages, which contain backported fixes for these issues.

New libtiff packages are available for Slackware 9.0, 9.1, 10.0, 10.1, 10.2, and -current to fix security issues. These issues could be used to crash programs linked to libtiff or possibly to execute code as the program's user. Thanks to Tavis Ormandy and the Google Security Team.

From Red Hat Security Advisory 2006:0648 :

Updated kdegraphics packages that fix several security flaws in kfax are now available for Red Hat Enterprise Linux 2.1, and 3.

This update has been rated as having moderate security impact by the Red Hat Security Response Team.

The kdegraphics package contains graphics applications for the K Desktop Environment.

Tavis Ormandy of Google discovered a number of flaws in libtiff during a security audit. The kfax application contains a copy of the libtiff code used for parsing TIFF files and is therefore affected by these flaws. An attacker who has the ability to trick a user into opening a malicious TIFF file could cause kfax to crash or possibly execute arbitrary code. (CVE-2006-3459, CVE-2006-3460, CVE-2006-3461, CVE-2006-3462, CVE-2006-3463, CVE-2006-3464, CVE-2006-3465)

Red Hat Enterprise Linux 4 is not vulnerable to these issues as kfax uses the shared libtiff library which has been fixed in a previous update.

Users of kfax should upgrade to these updated packages, which contain backported patches and are not vulnerable to this issue.

Updated kdegraphics packages that fix several security flaws in kfax are now available for Red Hat Enterprise Linux 2.1, and 3.

This update has been rated as having moderate security impact by the Red Hat Security Response Team.

The kdegraphics package contains graphics applications for the K Desktop Environment.

Tavis Ormandy of Google discovered a number of flaws in libtiff during a security audit. The kfax application contains a copy of the libtiff code used for parsing TIFF files and is therefore affected by these flaws. An attacker who has the ability to trick a user into opening a malicious TIFF file could cause kfax to crash or possibly execute arbitrary code. (CVE-2006-3459, CVE-2006-3460, CVE-2006-3461, CVE-2006-3462, CVE-2006-3463, CVE-2006-3464, CVE-2006-3465)

Red Hat Enterprise Linux 4 is not vulnerable to these issues as kfax uses the shared libtiff library which has been fixed in a previous update.

Users of kfax should upgrade to these updated packages, which contain backported patches and are not vulnerable to this issue.

From Red Hat Security Advisory 2006:0603 :

Updated libtiff packages that fix several security flaws are now available for Red Hat Enterprise Linux.

This update has been rated as having important security impact by the Red Hat Security Response Team.

The libtiff package contains a library of functions for manipulating TIFF (Tagged Image File Format) files.

Tavis Ormandy of Google discovered a number of flaws in libtiff during a security audit. An attacker could create a carefully crafted TIFF file in such a way that it was possible to cause an application linked with libtiff to crash or possibly execute arbitrary code.
(CVE-2006-3459, CVE-2006-3460, CVE-2006-3461, CVE-2006-3462, CVE-2006-3463, CVE-2006-3464, CVE-2006-3465)

All users are advised to upgrade to these updated packages, which contain backported fixes for these issues.

Tavis Ormandy, Google Security Team, discovered several vulnerabilities the libtiff image processing library :

Several buffer overflows have been discovered, including a stack buffer overflow via TIFFFetchShortPair() in tif_dirread.c, which is used to read two unsigned shorts from the input file. While a bounds check is performed via CheckDirCount(), no action is taken on the result allowing a pathological tdir_count to read an arbitrary number of unsigned shorts onto a stack buffer. (CVE-2006-3459)

A heap overflow vulnerability was discovered in the jpeg decoder, where TIFFScanLineSize() is documented to return the size in bytes that a subsequent call to TIFFReadScanline() would write, however the encoded jpeg stream may disagree with these results and overrun the buffer with more data than expected. (CVE-2006-3460)

Another heap overflow exists in the PixarLog decoder where a run length encoded data stream may specify a stride that is not an exact multiple of the number of samples. The result is that on the final decode operation the destination buffer is overrun, potentially allowing an attacker to execute arbitrary code. (CVE-2006-3461)

The NeXT RLE decoder was also vulnerable to a heap overflow vulnerability, where no bounds checking was performed on the result of certain RLE decoding operations. This was solved by ensuring the number of pixels written did not exceed the size of the scanline buffer already prepared. (CVE-2006-3462)

An infinite loop was discovered in EstimateStripByteCounts(), where a 16bit unsigned short was used to iterate over a 32bit unsigned value, should the unsigned int (td_nstrips) have exceeded USHORT_MAX, the loop would never terminate and continue forever. (CVE-2006-3463)

Multiple unchecked arithmetic operations were uncovered, including a number of the range checking operations deisgned to ensure the offsets specified in tiff directories are legitimate. These can be caused to wrap for extreme values, bypassing sanity checks. Additionally, a number of codepaths were uncovered where assertions did not hold true, resulting in the client application calling abort(). (CVE-2006-3464)

A flaw was also uncovered in libtiffs custom tag support, as documented here http://www.libtiff.org/v3.6.0.html. While well formed tiff files must have correctly ordered directories, libtiff attempts to support broken images that do not. However in certain circumstances, creating anonymous fields prior to merging field information from codec information can result in recognised fields with unexpected values. This state results in abnormal behaviour, crashes, or potentially arbitrary code execution. (CVE-2006-3465)

The updated packages have been patched to correct these issues.

This update of libtiff is the result of a source-code audit done by Tavis Ormandy. It fixes various bugs that can lead to denial-of-service conditions as well as to remote code execution while parsing a tiff image. (CVE-2006-3459 / CVE-2006-3460 / CVE-2006-3461 / CVE-2006-3462 / CVE-2006-3463 / CVE-2006-3464 / CVE-2006-3465)

Please restart your applications.

Tavis Ormandy of the Google Security Team discovered several problems in the TIFF library. The Common Vulnerabilities and Exposures project identifies the following issues :

  - CVE-2006-3459     Several stack-buffer overflows have been discovered.

  - CVE-2006-3460     A heap overflow vulnerability in the JPEG decoder may     overrun a buffer with more data than expected.

  - CVE-2006-3461     A heap overflow vulnerability in the PixarLog decoder     may allow an attacker to execute arbitrary code.

  - CVE-2006-3462     A heap overflow vulnerability has been discovered in the     NeXT RLE decoder.

  - CVE-2006-3463     An loop was discovered where a 16bit unsigned short was     used to iterate over a 32bit unsigned value so that the     loop would never terminate and continue forever.

  - CVE-2006-3464     Multiple unchecked arithmetic operations were uncovered,     including a number of the range checking operations     designed to ensure the offsets specified in TIFF     directories are legitimate.

  - CVE-2006-3465     A flaw was also uncovered in libtiffs custom tag support     which may result in abnormal behaviour, crashes, or     potentially arbitrary code execution.

ID	Name	Product	Family	Published	Updated	Severity
27334	openSUSE 10 Security Update : libtiff (libtiff-1907)	Nessus	SuSE Local Security Checks	10/17/2007	1/14/2021	high
206852	NewStart CGSL MAIN 6.02 : libtiff Multiple Vulnerabilities (NS-SA-2024-0051)	Nessus	NewStart CGSL Local Security Checks	9/10/2024	9/10/2024	high
27909	Ubuntu 5.04 / 5.10 / 6.06 LTS : tiff vulnerabilities (USN-330-1)	Nessus	Ubuntu Local Security Checks	11/10/2007	1/19/2021	high
22165	GLSA-200608-07 : libTIFF: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	8/7/2006	1/6/2021	high
22149	RHEL 2.1 / 3 / 4 : libtiff (RHSA-2006:0603)	Nessus	Red Hat Local Security Checks	8/4/2006	1/14/2021	high
22236	Slackware 10.0 / 10.1 / 10.2 / 9.0 / 9.1 / current : libtiff (SSA:2006-230-01)	Nessus	Slackware Local Security Checks	8/21/2006	1/14/2021	high
67404	Oracle Linux 3 : kdegraphics (ELSA-2006-0648)	Nessus	Oracle Linux Local Security Checks	7/12/2013	1/14/2021	high
22282	CentOS 3 : kdegraphics (CESA-2006:0648)	Nessus	CentOS Local Security Checks	8/30/2006	1/4/2021	high
67398	Oracle Linux 3 : libtiff (ELSA-2006-0603)	Nessus	Oracle Linux Local Security Checks	7/12/2013	1/14/2021	high
22161	CentOS 3 / 4 : libtiff (CESA-2006:0603)	Nessus	CentOS Local Security Checks	8/7/2006	1/4/2021	high
22293	RHEL 2.1 / 3 : kdegraphics (RHSA-2006:0648)	Nessus	Red Hat Local Security Checks	8/30/2006	1/14/2021	high
23886	Mandrake Linux Security Advisory : libtiff (MDKSA-2006:137)	Nessus	Mandriva Local Security Checks	12/16/2006	1/6/2021	high
29512	SuSE 10 Security Update : libtiff (ZYPP Patch Number 1908)	Nessus	SuSE Local Security Checks	12/13/2007	1/14/2021	high
22679	Debian DSA-1137-1 : tiff - several vulnerabilities	Nessus	Debian Local Security Checks	10/14/2006	1/4/2021	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high

high

high

high

high

high