Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Predictor heap-buffer-overflow in libtiff 4.0.6

IdentifiersCVE-2016-9535CWE-122

CVE-2016-9535 affects tif_predict.h and tif_predict.c in libtiff 4.0.6. The vulnerability is triggered when processing crafted TIFF data with unusual tile sizing, including YCbCr images with subsampling. The affected predictor logic contains assertions that may abort in debug builds, but in release builds the same conditions can result in a heap-based buffer overflow. The issue has been reported as MSVR 35105 and is also referred to as "Predictor heap-buffer-overflow." The provided content further characterizes the issue as allowing arbitrary code execution.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause an assertion failure and process termination in debug configurations, resulting in denial of service. In release builds, the flaw can lead to a heap buffer overflow during TIFF parsing, which may permit memory corruption and potentially arbitrary code execution in the context of the application using libtiff.

Mitigation

If you can’t patch tonight, do this now.

Until patches are applied, avoid processing untrusted TIFF files, especially those using unusual tile sizes or YCbCr subsampling. Disable or restrict TIFF parsing in exposed workflows where feasible, sandbox applications that ingest image content, and use exploit-detection or content-filtering controls to reduce exposure. Monitoring for crashes or anomalous behavior in image-processing services may help identify exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade libtiff from affected version 4.0.6 to a fixed release provided by the vendor or downstream distributor. Rebuild and redeploy any applications statically or dynamically linked against the vulnerable libtiff version. Apply vendor patches from operating system and application maintainers where libtiff is bundled as a dependency.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LibtiffLibtiffapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.