Loading vulnerability…
WinFTP FTP Server 2.3.0 is vulnerable to a denial of service condition when operating in passive (PASV) mode. An authenticated remote user can trigger the vulnerability by initiating a sequence of FTP sessions and issuing the invalid command 'NLST -1'. This causes the server to become unresponsive or crash, resulting in a denial of service.
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 WinFTP 2.3.0 (CVE-2008-5666). The exploit requires valid FTP credentials (anonymous access is sufficient if NLST is permitted) and connects to the target FTP server on TCP port 21. After logging in and entering passive mode, it sends an NLST command with a very large argument ('..?' repeated 35,000 times), which causes the WinFTP service to crash. The module is written in Ruby and leverages Metasploit's auxiliary and remote FTP libraries. The exploit is a proof-of-concept and does not provide post-exploitation capabilities or a customizable payload. The structure is typical for a Metasploit DoS module, with a single entry point and clear targeting of a specific product and version.
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.