A stack consumption vulnerability exists in the FTP Service of Microsoft Internet Information Services (IIS) versions 5.0 through 7.0. The vulnerability is triggered when a remote authenticated user issues a 'ls -R' command with a wildcard referencing a subdirectory, followed by a '..' (dot dot), causing the service to recurse indefinitely and consume stack space, ultimately leading to a daemon crash.
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 auxiliary module targeting a Denial of Service (DoS) vulnerability in Microsoft IIS FTP Server versions 5.0 through 7.0 (CVE-2009-2521). The exploit works by sending a recursive 'LIST -R */../' command via FTP, which can exhaust the stack and crash the FTP service. The module requires valid FTP credentials and certain server configurations (FTP Publishing in manual mode, at least one directory under the FTP root, or write-access to create one). The code is written in Ruby and leverages Metasploit's FTP and DoS auxiliary libraries. The main attack vector is network-based, targeting the FTP service (typically on TCP port 21). The module is a proof-of-concept for causing a service crash and does not provide post-exploitation capabilities.
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.