Loading vulnerability…
A stack-based buffer overflow exists in Trellian FTP client versions 3.01 and 3.1.3.1789. The vulnerability is triggered when the client processes an overly long PASV response from a remote FTP server, leading to a buffer overflow on the stack. This can be exploited by a malicious FTP server to execute arbitrary code on the client 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 (1 hidden).
This repository contains a single Metasploit module that exploits a buffer overflow vulnerability in Trellian FTP Client version 3.01 (CVE-2010-1465). The exploit works by acting as a malicious FTP server: when a vulnerable client connects and issues a PASV command, the server responds with an excessively long PASV message that overflows a buffer in the client. This allows the attacker to execute arbitrary code on the victim's machine. The module is written in Ruby and leverages the Metasploit framework's TcpServer mixin to handle incoming FTP connections. The payload is customizable and can be any Metasploit-compatible payload up to 900 bytes, avoiding certain bad characters. The only network endpoint involved is the attacker's machine listening on TCP port 21, mimicking a legitimate FTP server. The exploit targets Windows XP systems running Trellian FTP Client 3.01. The repository is operational and ready for use within the Metasploit framework.
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.