CVE-2001-0333 is a directory traversal flaw in Microsoft Internet Information Services (IIS) 5.0 and earlier caused by improper handling of percent-encoded path characters. IIS applies security checks after an initial decode pass, but then decodes the filename again. By double-encoding traversal sequences such as dot-dot and backslash characters, a remote attacker can bypass path validation and cause the final resolved path to reference files or executable resources outside the web root. The provided context states that this behavior allowed attackers to reach unintended locations and execute arbitrary commands.
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 (8 hidden).
This repository contains a single Metasploit module (ms01_026_dbldecode.rb) that exploits the Microsoft IIS/PWS CGI Filename Double Decode vulnerability (MS01-026, CVE-2001-0333). The exploit targets vulnerable IIS servers (commonly on Windows 2000) by abusing double URL decoding in the scripts directory, allowing remote attackers to execute arbitrary commands or drop a payload executable. The module supports both direct command execution and dropping a custom payload (such as a reverse shell) using Metasploit's command stager. The exploit interacts with the target over HTTP, specifically targeting the /scripts/ directory, and leaves artifacts (payload executables) on disk. The code is written in Ruby and is fully integrated into the Metasploit framework, making it weaponized and easily customizable for different payloads and configurations.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.