Loading vulnerability…
A flaw exists in the check_chunk_name() function of pngcheck version 2.4.0. The vulnerability allows an attacker to craft a malicious PNG file that, when processed by pngcheck, can trigger a temporary denial of service condition. The issue is due to improper input validation within the check_chunk_name() function.
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 provides a comprehensive set of proof-of-concept (POC) exploits for multiple vulnerabilities in the pngcheck utility (versions 2.4.0, 3.0.0, and 3.0.1), including CVE-2020-27818 and CVE-2020-35511. The structure is organized by vulnerability and version, with each subdirectory containing a README, a Python script to generate malicious PNG or MNG files, and references to the vulnerabilities. The main exploit capability is the generation of crafted image files that, when processed by vulnerable versions of pngcheck, trigger out-of-bounds reads, buffer over-reads, or null pointer dereferences, leading to application crashes or denial of service. The exploits are local in nature, requiring the attacker to convince a user or process to analyze a malicious file with pngcheck. The repository does not contain weaponized or remote exploits, but provides high-quality POC scripts and detailed documentation for each vulnerability. No network endpoints or remote services are targeted; all attacks are file-based. The code is primarily in Python, with one patch file for enabling AddressSanitizer. The repository is well-structured for vulnerability research and testing.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.