Loading vulnerability…
A stack-based buffer overflow exists in the ERM_convert_to_correct_webpath function within ermapper_u.dll in ERDAS ER Viewer versions prior to 13.00.0001. The vulnerability is triggered when a specially crafted pathname in an ERS file is processed, leading to a buffer overflow condition.
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 targeting a buffer overflow vulnerability (CVE-2013-0726) in ERS Viewer 2011 (version 11.04) for Windows. The exploit abuses improper handling of user-supplied data in the ermapper_u.dll (specifically the ERM_convert_to_correct_webpath function) by generating a malicious .ers file. When this file is opened by a user in the vulnerable ERS Viewer, arbitrary code execution is achieved under the user's context. The module allows the attacker to specify a payload (such as a reverse shell), which is embedded in the crafted .ers file. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The attack vector is local, requiring user interaction to open the malicious file. The only fingerprintable endpoints are the .ers file format and the vulnerable DLL. The code is well-structured, with clear separation of initialization, payload construction, and file creation.
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.