Loading vulnerability…
A heap-based buffer overflow exists in the png_combine_row function in libpng versions before 1.5.21 and 1.6.x before 1.6.16. On 64-bit systems, this vulnerability can be triggered by processing a specially crafted 'very wide interlaced' PNG image, potentially allowing context-dependent attackers to execute arbitrary code.
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 repository is a comprehensive security research project focused on fuzzing and exploiting vulnerabilities in the libpng library, specifically targeting CVE-2014-9495 (heap buffer overflow in Adam7 interlaced PNG processing). The structure is divided into several parts: - Part 1: Fuzzing experiments using OSS-Fuzz and coverage analysis scripts, with and without a seed corpus, to measure code coverage improvements. - Part 3: Custom fuzzer improvements, including enhanced read and write fuzzers for libpng, with detailed coverage reports. - Part 4: Exploitation of CVE-2014-9495 using a proof-of-concept C program (write_exploit.c) and a shell script (run.poc.sh) that builds a vulnerable version of libpng, compiles the exploit, and demonstrates the crash using AddressSanitizer. The main exploit capability is the generation of a malformed PNG file that triggers a heap buffer overflow in libpng 1.5.20. The exploit is operational and demonstrates the vulnerability in a controlled environment. The repository also includes scripts for building, running, and cleaning up the test environment, as well as detailed documentation and coverage reports. No network endpoints are involved; the attack vector is a crafted file processed by a vulnerable library.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.