FileZilla Server before 0.9.22 contains a remotely triggerable denial-of-service flaw in its handling of FTP command arguments. According to the provided vulnerability record, a wildcard argument supplied to the LIST or NLST commands can trigger a NULL pointer dereference and crash the server. The record also notes CVE analysis suggesting the issue might instead be related to a malformed PORT command, so the exact triggering input is not fully certain from the available information. In either case, the vulnerability affects FileZilla Server versions prior to 0.9.22 and results in process termination due to dereferencing a NULL pointer during command processing.
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 (1 hidden).
This repository contains a single Metasploit auxiliary module targeting a denial of service (DoS) vulnerability in FileZilla FTP Server versions 0.9.21 and earlier (CVE-2006-6565). The exploit works by sending a malformed PORT command followed by a LIST command to the FTP server, which causes the server to attempt to write to a NULL pointer, resulting in a crash. The module is written in Ruby and leverages Metasploit's FTP and DoS auxiliary components. The only file present is the exploit module itself, which is structured with an initialization method providing metadata and a 'run' method that performs the attack sequence. The attack vector is network-based, requiring access to the FTP service (typically on TCP port 21). No payload is delivered; the exploit's sole purpose is to crash the target service, making it a proof-of-concept (POC) DoS exploit.
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 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.