Loading vulnerability…
A buffer overflow vulnerability exists in FileCOPA FTP Server versions prior to 1.01 (released on 18th July 2006). The vulnerability is triggered when a remote authenticated attacker sends an excessively long argument to the LIST command, resulting in a buffer overflow condition. This can allow the attacker to overwrite memory and potentially execute arbitrary code on the server.
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 module targeting a buffer overflow vulnerability in the FileCopa FTP Server (versions prior to July 18, 2006). The exploit abuses the LIST command to trigger a stack-based buffer overflow, allowing arbitrary code execution. The module is written in Ruby and leverages the Metasploit framework's FTP mixin for connectivity and payload delivery. It supports two specific Windows targets: Windows 2000 Server SP4 English and Windows XP Pro SP2 Italian, each with a hardcoded return address for reliable exploitation. The payload is customizable (up to 400 bytes) and filtered for bad characters. The exploit requires valid FTP credentials and network access to the target service. The only fingerprintable endpoint is the FTP service, typically running on TCP port 21. The repository is operational and provides a working exploit for CVE-2006-3726.
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.