Loading vulnerability…
A stack-based buffer overflow exists in the JPEG2000 plugin in IrfanView PlugIns prior to version 4.33. The vulnerability is triggered when processing a JPEG2000 (JP2) file containing a specially crafted Quantization Default (QCD) marker segment, which can cause the application to overwrite stack memory and potentially allow execution of 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 contains a single Metasploit module (Ruby file) that exploits a stack-based buffer overflow vulnerability (CVE-2012-0897) in Irfanview's JPEG2000.dll plugin (version 4.32 and possibly others) on Windows. The exploit works by generating a specially crafted .jp2 (JPEG2000) image file that, when opened in the vulnerable Irfanview application, triggers a buffer overflow and executes arbitrary code. The module uses an egghunter for payload stability and allows the attacker to specify a custom payload (e.g., reverse shell, meterpreter). The attack vector is local, requiring the victim to open the malicious file. The main fingerprintable endpoint is the generated .jp2 file, and the exploit specifically targets the i_view32.exe binary and its associated plugin. The repository is operational and part of the Metasploit framework, with a clear structure and purpose focused on weaponized file format exploitation.
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.