Loading vulnerability…
A stack-based buffer overflow exists in the rf_report_error function within ermapper_u.dll in Intergraph ERDAS ER Viewer versions prior to 13.0.1.1301. The vulnerability is triggered when a specially crafted ERS file containing an overly long string 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-3482) in ERS Viewer 2013 (version 13.0.0.1151) for Windows. The exploit works by generating a malicious .ers file that, when opened by a user in the vulnerable application, triggers a buffer overflow in the ermapper_u.dll (specifically in the rf_report_error function). The module supports both non-DEP/ASLR and DEP/ASLR bypass techniques using ROP chains and egghunter shellcode. The payload is customizable via Metasploit and allows for arbitrary code execution under the context of the user opening the file. The attack vector is local, requiring user interaction to open the crafted file. The main fingerprintable endpoints are the .ers file format and the vulnerable DLLs (ermapper_u.dll and ethrlib.dll). The repository is structured as a standard Metasploit exploit module written in Ruby, with all exploit logic contained in a single file.
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.