In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE:
    there is a third-party report of inability to reproduce this issue (CVE-2017-17973)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE:
    there is a third-party report of inability to reproduce this issue (CVE-2017-17973)

Note that Nessus relies on the presence of the package as reported by the vendor.

An update of the libtiff package has been released.

This update for tiff fixes the following issues :

  - CVE-2017-9935: There was a heap-based buffer overflow in     the t2p_write_pdf function in tools/tiff2pdf.c. This     heap overflow could lead to different damages. For     example, a crafted TIFF document can lead to an     out-of-bounds read in TIFFCleanup, an invalid free in     TIFFClose or t2p_free, memory corruption in     t2p_readwrite_pdf_image, or a double free in t2p_free.
    Given these possibilities, it probably could cause     arbitrary code execution (bsc#1046077)

  - CVE-2017-17973: There is a heap-based use-after-free in     the t2p_writeproc function in tiff2pdf.c. (bsc#1074318)

  - CVE-2018-5784: There is an uncontrolled resource     consumption in the TIFFSetDirectory function of     tif_dir.c. Remote attackers could leverage this     vulnerability to cause a denial of service via a crafted     tif file. This occurs because the declared number of     directory entries is not validated against the actual     number of directory entries (bsc#1081690)

This update was imported from the SUSE:SLE-12:Update update project.

This update for tiff fixes the following issues :

  - CVE-2017-9935: There was a heap-based buffer overflow in     the t2p_write_pdf function in tools/tiff2pdf.c. This     heap overflow could lead to different damages. For     example, a crafted TIFF document can lead to an     out-of-bounds read in TIFFCleanup, an invalid free in     TIFFClose or t2p_free, memory corruption in     t2p_readwrite_pdf_image, or a double free in t2p_free.
    Given these possibilities, it probably could cause     arbitrary code execution (bsc#1046077)

  - CVE-2017-17973: There is a heap-based use-after-free in     the t2p_writeproc function in tiff2pdf.c. (bsc#1074318)

  - CVE-2018-5784: There is an uncontrolled resource     consumption in the TIFFSetDirectory function of     tif_dir.c. Remote attackers could leverage this     vulnerability to cause a denial of service via a crafted     tif file. This occurs because the declared number of     directory entries is not validated against the actual     number of directory entries (bsc#1081690)

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

This update for tiff fixes the following issues :

  - CVE-2016-9453: The t2p_readwrite_pdf_image_tile function     allowed remote attackers to cause a denial of service     (out-of-bounds write and crash) or possibly execute     arbitrary code via a JPEG file with a TIFFTAG_JPEGTABLES     of length one (bsc#1011107).

  - CVE-2016-5652: An exploitable heap-based buffer overflow     existed in the handling of TIFF images in the TIFF2PDF     tool. A crafted TIFF document can lead to a heap-based     buffer overflow resulting in remote code execution.
    Vulnerability can be triggered via a saved TIFF file     delivered by other means (bsc#1007280).

  - CVE-2017-11335: There is a heap-based buffer overflow in     tools/tiff2pdf.c via a PlanarConfig=Contig image, which     caused a more than one hundred bytes out-of-bounds write     (related to the ZIPDecode function in tif_zip.c). A     crafted input may lead to a remote denial of service     attack or an arbitrary code execution attack     (bsc#1048937).

  - CVE-2016-9536: tools/tiff2pdf.c had an out-of-bounds     write vulnerabilities in heap allocated buffers in     t2p_process_jpeg_strip(). Reported as MSVR 35098, aka     't2p_process_jpeg_strip heap-buffer-overflow.'     (bsc#1011845)

  - CVE-2017-9935: In LibTIFF, there was a heap-based buffer     overflow in the t2p_write_pdf function in     tools/tiff2pdf.c. This heap overflow could lead to     different damages. For example, a crafted TIFF document     can lead to an out-of-bounds read in TIFFCleanup, an     invalid free in TIFFClose or t2p_free, memory corruption     in t2p_readwrite_pdf_image, or a double free in     t2p_free. Given these possibilities, it probably could     cause arbitrary code execution (bsc#1046077).

  - CVE-2017-17973: There is a heap-based use-after-free in     the t2p_writeproc function in tiff2pdf.c. (bsc#1074318)

  - CVE-2015-7554: The _TIFFVGetField function in tif_dir.c     allowed attackers to cause a denial of service (invalid     memory write and crash) or possibly have unspecified     other impact via crafted field data in an extension tag     in a TIFF image (bsc#960341).

  - CVE-2016-5318: Stack-based buffer overflow in the
    _TIFFVGetField function allowed remote attackers to     crash the application via a crafted tiff (bsc#983436).

  - CVE-2016-10095: Stack-based buffer overflow in the
    _TIFFVGetField function in tif_dir.c allowed remote     attackers to cause a denial of service (crash) via a     crafted TIFF file (bsc#1017690,).

  - CVE-2016-10268: tools/tiffcp.c allowed remote attackers     to cause a denial of service (integer underflow and     heap-based buffer under-read) or possibly have     unspecified other impact via a crafted TIFF image,     related to 'READ of size 78490' and     libtiff/tif_unix.c:115:23 (bsc#1031255)

  - An overlapping of memcpy parameters was fixed which     could lead to content corruption (bsc#1017691).

  - Fixed an invalid memory read which could lead to a crash     (bsc#1017692).

  - Fixed a NULL pointer dereference in TIFFReadRawData     (tiffinfo.c) that could crash the decoder (bsc#1017688).

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

ID	Name	Product	Family	Type	Severity
464206	Echo: tiff: security update to 4.7.0	Tenable Cloud Security	Echo Local Security Checks	Local	high
464206	Echo: tiff: security update to 4.7.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
221044	Linux Distros Unpatched Vulnerability : CVE-2017-17973	Nessus	Misc.	Local	high
121910	Photon OS 2.0: Libtiff PHSA-2018-2.0-0013	Nessus	PhotonOS Local Security Checks	Local	high
109716	openSUSE Security Update : tiff (openSUSE-2018-443)	Nessus	SuSE Local Security Checks	Local	high
109675	SUSE SLED12 / SLES12 Security Update : tiff (SUSE-SU-2018:1180-1)	Nessus	SuSE Local Security Checks	Local	high
109674	SUSE SLES11 Security Update : tiff (SUSE-SU-2018:1179-1)	Nessus	SuSE Local Security Checks	Local	critical

Detections

Analytics

CVE-2017-17973

high

Tenable Plugins

high

high

high

high

high

high

critical