Loading vulnerability…
A buffer overflow vulnerability exists in Microsoft HTML Help Workshop 4.74 and earlier, where a specially crafted .hhp file with an overly long 'Index file' field can trigger a buffer overflow. This may be related to a previously reported issue (CVE-2006-0564).
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 (6 hidden).
This repository contains a single Metasploit module targeting a stack buffer overflow vulnerability (CVE-2009-0133) in Microsoft HTML Help Workshop 4.74. The exploit works by generating a specially crafted .hhp project file (default name: msf.hhp) that, when opened by a user in the vulnerable application on Windows XP SP3, triggers a buffer overflow and executes arbitrary code. The module uses Metasploit's egghunter technique to deliver the payload, which can be any Metasploit-compatible shellcode up to 1024 bytes, avoiding certain bad characters. The exploit is user-assisted (requires the victim to open the malicious file) and does not target network services. The repository is structured as a single Ruby file within the Metasploit framework, leveraging its file format and egghunter exploit mixins. No network endpoints or remote services are targeted; the main fingerprintable artifact is the malicious .hhp 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.