Loading vulnerability…
A heap-based buffer overflow exists in the MaskedEdit ActiveX control (Msmask32.ocx) versions prior to 6.0.84.18, as used in Microsoft Visual Studio 6.0, Visual Basic 6.0, Visual Studio .NET 2002 SP1 and 2003 SP1, and Visual FoxPro 8.0 SP1 and 9.0 SP1/SP2. The vulnerability is triggered by supplying an overly long value to the 'Mask' parameter, due to insufficient boundary checking of property values. This flaw allows remote attackers to execute arbitrary code in the context of the user running the vulnerable control, typically via a malicious web page.
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 (2 hidden).
This repository contains a single Metasploit module targeting a stack buffer overflow vulnerability (CVE-2008-3704) in the Mdmask32.ocx ActiveX control, part of Microsoft Visual Studio 6.0. The exploit is weaponized and leverages the Metasploit framework's HTTP server capabilities to serve a malicious HTML/JavaScript page. When a vulnerable client (Windows XP with IE6 and the affected ActiveX control) visits the attacker's page, a specially crafted 'Mask' parameter triggers a buffer overflow, allowing arbitrary code execution. The default payload is a reverse TCP shell, but any compatible Metasploit payload can be used. The module is well-structured, with randomized JavaScript variable names to evade detection, and is designed for use in client-side attacks via the browser. The main fingerprintable endpoints are the HTTP path (default '/'), the vulnerable file (Mdmask32.ocx), and the CLSID of the ActiveX control.
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.