Loading vulnerability…
A buffer overflow vulnerability exists in Ayukov NFTPD version 2.0 and earlier, which allows remote attackers to execute arbitrary code. The vulnerability is due to improper bounds checking on user-supplied input, leading to a stack-based buffer overflow.
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 module (modules/exploits/windows/ftp/ayukov_nftp.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2017-15222) in Ayukov NFTP FTP Client 2.0 and earlier. The exploit works by running a malicious FTP server that, when connected to by a vulnerable client, responds to the SYST command with an overly long string, triggering the buffer overflow. The module allows the attacker to deliver a customizable Metasploit payload (such as a reverse shell) to the victim, potentially resulting in arbitrary code execution under the context of the user running the FTP client. The module is weaponized, as it is part of the Metasploit framework and supports flexible payload selection. The only network endpoint is the attacker's server, which listens on a configurable TCP port (default 21). The code is written in Ruby and follows the standard Metasploit exploit module structure.
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.