CVE-2016-9273 in LibTIFFinfo

Summary

by MITRE

tiffsplit in libtiff 4.0.6 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted file, related to changing td_nstrips in TIFF_STRIPCHOP mode.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 05/13/2026

The vulnerability identified as CVE-2016-9273 affects the tiffsplit utility within libtiff version 4.0.6, representing a critical security flaw that enables remote attackers to execute denial of service attacks through out-of-bounds read conditions. This vulnerability specifically manifests when processing specially crafted TIFF files in TIFF_STRIPCHOP mode, where the software fails to properly validate input parameters before attempting to modify the td_nstrips attribute. The flaw resides in the improper handling of image strip data structures during file processing, creating a scenario where malicious input can trigger memory access violations that crash the application.

The technical implementation of this vulnerability stems from insufficient boundary checking within the tiffsplit utility's processing logic. When operating in TIFF_STRIPCHOP mode, the software attempts to calculate and adjust the number of strips in a TIFF image, but fails to validate whether the calculated values remain within acceptable bounds for the td_nstrips parameter. This oversight creates a condition where an attacker can craft a malicious TIFF file containing malformed strip count data that, when processed by tiffsplit, results in reading memory locations beyond the allocated buffer boundaries. The out-of-bounds read occurs because the software assumes valid input parameters without proper validation, leading to unpredictable memory access patterns that ultimately cause application termination.

From an operational perspective, this vulnerability presents significant risks to systems that rely on libtiff for image processing tasks, particularly those exposed to untrusted input sources such as web applications, file upload systems, or document processing services. The denial of service impact means that legitimate users cannot process TIFF files through affected systems, potentially disrupting business operations and creating availability issues. Attackers can exploit this vulnerability remotely by simply providing a maliciously crafted TIFF file to any system running the vulnerable tiffsplit utility, making it particularly dangerous in environments where automatic file processing occurs. The vulnerability affects not only direct command-line usage but also any application or service that incorporates libtiff functionality, amplifying its potential impact across various software ecosystems.

The vulnerability aligns with CWE-129, which addresses insufficient validation of length of input buffers, and represents a classic example of improper input validation leading to memory safety issues. From an ATT&CK framework perspective, this vulnerability maps to T1499.004, which covers the use of denial of service techniques through memory corruption, and T1595.001 for reconnaissance activities involving identifying vulnerable software components. Organizations should prioritize updating to libtiff versions that have addressed this vulnerability, typically libtiff 4.0.7 or later, which includes proper bounds checking and input validation mechanisms. Additionally, implementing proper file validation, sandboxing file processing operations, and restricting access to vulnerable utilities can provide additional layers of protection. Network segmentation and monitoring for unusual file processing activities can help detect potential exploitation attempts, while regular security assessments should verify that all systems utilizing libtiff components have been properly patched and updated to prevent exploitation of this and similar memory safety vulnerabilities.

Reservation

11/11/2016

Disclosure

01/18/2017

Moderation

accepted

Entry

VDB-95520

CPE

ready

EPSS

0.00483

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!