The StopModule method in the NTR ActiveX control (prior to version 2.0.4.8) contains a vulnerability where the lModule parameter is insufficiently validated, allowing an attacker to supply a crafted value. This value is subsequently used as a function pointer, enabling execution of arbitrary code at an attacker-controlled memory address.
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 remote code execution vulnerability (CVE-2012-0267) in the NTR ActiveX 1.1.8.0 control, specifically in the StopModule() method. The exploit is delivered via a malicious HTML page served by the attacker's HTTP server. When a victim using Internet Explorer 6 or 7 on Windows XP SP3 or Windows Vista visits the page, JavaScript heap spraying is used to prepare memory, and the vulnerable ActiveX control is invoked with a crafted parameter, leading to arbitrary code execution. The module allows the attacker to deliver any Metasploit payload, such as a reverse shell or meterpreter session. The main entry point is the 'on_request_uri' method, which handles incoming HTTP requests and serves the exploit page. The exploit is operational and customizable, but requires the victim to have the vulnerable ActiveX control installed and to visit the attacker's page.
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.