SEGGER FTP Server for Windows versions prior to 3.22a contains a vulnerability where remote attackers can crash the FTP daemon by sending invalid LIST, STOR, or RETR commands. The vulnerability is due to improper input validation of these FTP commands, leading to a denial of service condition.
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 Python proof-of-concept exploit for CVE-2018-7449, targeting SEGGER embOS/IP FTP Server version 3.22. The exploit consists of two main code files: 'exploitFTPModule.py', which implements the core logic for interacting with the FTP server and sending malicious commands, and 'run-exploit.py', which serves as the entry point and handles argument parsing and execution flow. The exploit requires valid FTP credentials and a reachable FTP server (firewall disabled or compromised). Upon successful authentication, it sends a sequence of malformed FTP commands (STOR, LIST, RETR with crafted arguments) that cause the FTP daemon to crash, resulting in a denial of service. The README provides usage instructions and context, referencing the original exploit inspiration. No hardcoded IPs or credentials are present; the target and credentials are supplied at runtime. The exploit is not weaponized but serves as a functional proof-of-concept for the described vulnerability.
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.