Loading vulnerability…
A buffer overflow vulnerability exists in the FTP Service of Microsoft Internet Information Services (IIS) versions 5.0 through 6.0. The vulnerability is triggered when a remote authenticated user sends a specially crafted NLST (NAME LIST) command containing wildcards, resulting in memory corruption. This flaw allows for remote code execution or denial of service on the affected system.
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 (ms09_053_ftpd_nlst.rb) that exploits a stack buffer overflow vulnerability (CVE-2009-3023) in the Microsoft IIS FTP Server (IIS 5.0) on Windows 2000. The exploit works by creating a long directory path and sending a specially crafted NLST command, triggering the overflow and allowing arbitrary code execution. The module requires the FTP server to be writeable and supports multiple language/region targets (English, Italian, Japanese). The payload is customizable via Metasploit and is delivered using FTP commands. The attack vector is network-based, targeting TCP port 21. The code is operational and suitable for real-world exploitation, provided the target configuration matches the requirements.
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.