A remote buffer overflow vulnerability exists in the .printer ISAPI filter (msw3prt.dll) of Microsoft Windows 2000 IIS 5.0. The flaw is triggered by sending a specially crafted HTTP Host header of approximately 420 bytes to the .printer ISAPI extension, resulting in a stack-based buffer overflow. This allows remote attackers to overwrite the EIP register and execute arbitrary code with SYSTEM privileges. The vulnerability is not logged by IIS, making detection difficult, and affects both default and Service Pack 1 installations of IIS 5.0.
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 (Ruby file) that exploits a buffer overflow vulnerability (CVE-2001-0241) in the Internet Printing Protocol ISAPI module of Microsoft IIS 5.0, as described in MS01-023. The exploit targets Windows 2000 Server and Professional (SP0-SP1) and works by sending a specially crafted HTTP request to the /NULL.printer endpoint, overflowing the Host header to execute arbitrary code. The module supports multiple language/region targets by providing specific return addresses for each. The default payload is a reverse shell, but any compatible Metasploit payload can be used. The exploit is weaponized, as it is part of the Metasploit framework and allows for easy payload customization. The code includes a check method to verify vulnerability and an exploit method to deliver the payload. The only fingerprintable endpoint is /NULL.printer, which is used both for detection and exploitation.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.