Loading vulnerability…
CVE-2023-52356 concerns a segmentation fault and reported heap-based buffer-overflow condition in libtiff's TIFFReadRGBATileExt() API. Processing a crafted TIFF can trigger the fault, resulting in an application crash and denial of service. The reported failure involved an underflowed source offset passed to memmove() when invalid tile row or column parameters were used. The libtiff maintainer disputed that the original proof of concept represented a security vulnerability, characterizing it as API misuse caused by invalid parameters, but additional row and column validation was merged upstream.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This four-file repository is an analysis and proof-of-concept lab for CVE-2023-52356 in libtiff's TIFFReadRGBATileExt. README.md documents the vulnerable and fixed commits, AddressSanitizer/GDB observations, root cause, patch behavior, and limitations of the reproducer. poc.cc is a C++ libFuzzer-compatible LLVMFuzzerTestOneInput harness that opens attacker-controlled TIFF data from an in-memory stream and iterates tiles. Its tile-count calculations incorrectly use TIFFGetField's success return value as a coordinate passed to TIFFComputeTile. This can overestimate the Y tile count and invoke TIFFReadRGBATileExt with y values beyond the image height. In vulnerable libtiff, img.height - row underflows as an unsigned value and later drives an invalid memmove source pointer, causing a crash. corrected_poc.c is a C reproducer that opens the local file triger_input_47 and derives tile counts directly from image and tile dimensions; it demonstrates that correct API use does not reproduce the crash. The repository contains no network activity, shell, command-execution, or post-exploitation payload. The documented issue is a local/file-driven memory-safety denial of service contingent on the harness supplying invalid API coordinates, rather than evidence that a TIFF file alone triggers the fault under correct application logic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability covered by an Alma Linux 9.2 security advisory/plugin. It has a CVSS v3 vector of CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating a remotely exploitable, low-complexity denial-of-service impact with no privileges or user interaction required.
A moderate-severity libtiff vulnerability in which TIFFReadRGBATileExt() can trigger a segmentation fault, resulting in denial of service when processing a crafted TIFF file.
A moderate-severity (CVSS 7.5) heap-based buffer overflow in libtiff's TIFFReadRGBATileExt() API. A crafted TIFF file can trigger a segmentation fault and remotely crash a consuming application, resulting in denial of service.
A moderate-severity libtiff vulnerability in TIFFReadRGBATileExt() that can trigger a segmentation fault and cause denial of service when processing TIFF data.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.