Loading vulnerability…
CVE-2004-0597 is a set of buffer overflow conditions in libpng 1.2.5 and earlier, also affecting products that bundle or link against those versions. The issue is triggered when an application processes a malformed PNG image containing crafted chunk data. Specifically, libpng does not properly validate the length of transparency chunk data in png_handle_tRNS(), and performs insufficient bounds checking in png_handle_sBIT() and png_handle_hIST(). According to CERT/CC, the latter flaws could permit a buffer overflow during a subsequent png_crc_read() operation. Because libpng is commonly used by image viewers, browsers, messaging clients, and other software, the vulnerability can be reached remotely wherever attacker-supplied PNG content is parsed.
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.
No valid public exploits. Mallory filtered out 3 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.