CVE-2017-6465 is a remote code execution vulnerability in FTPShell Client 6.53. When the client connects to an FTP server, it sends a PWD command by default. The client does not properly validate or bound-check the length of the server's response to that command, which can trigger a buffer overflow. A malicious or attacker-controlled FTP server can return an overlong PWD response and potentially corrupt memory in the client process, leading to code execution.
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: 'ftpshell51_pwd_reply.rb', which exploits a stack buffer overflow vulnerability (CVE-2017-6465) in FTPShell 5.1 running on Windows XP. The exploit works by running a malicious FTP server that delivers an overly long response to the PWD command. When a vulnerable FTPShell client connects and issues the PWD command, the server responds with a specially crafted directory string that overflows the client's stack, overwriting the saved EIP and SEH, and executes arbitrary code via an egghunter payload. The module leverages Metasploit's payload system, allowing the attacker to execute custom shellcode on the victim's machine. The only file in the repository is a Ruby script structured as a standard Metasploit exploit module, including all necessary metadata, target configuration, and exploit logic. No hardcoded IPs, URLs, or file paths are present; the main fingerprintable endpoint is the attacker's FTP server. The exploit is operational and can be used to gain code execution on vulnerable clients.
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.