Loading vulnerability…
Titan FTP Server 6.26 build 630 is vulnerable to a denial of service condition when a remote attacker sends the SITE WHO command. The server fails to properly handle this command, resulting in excessive CPU consumption and service disruption.
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 auxiliary module targeting a Denial of Service (DoS) vulnerability in Titan FTP Server version 6.26 build 630 (CVE-2008-6082). The exploit requires valid FTP credentials to authenticate to the target server. Once authenticated, it sends the 'SITE WHO' command, which causes the server to crash or become unresponsive. The module is written in Ruby and leverages Metasploit's FTP and DoS auxiliary components. The only file present is the exploit module itself, and it is structured to be used within the Metasploit framework. No hardcoded IPs or URLs are present; the target is specified by the user at runtime.
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.