Loading vulnerability…
CVE-2004-1602 is an observable timing discrepancy in ProFTPD 1.2.x, including 1.2.8 and 1.2.10. During username handling, the FTP service produces measurably different response times depending on whether the supplied username exists. A remote party can measure these differences to distinguish valid accounts from nonexistent accounts.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A timing-based username-enumeration information-disclosure vulnerability in ProFTPD 1.2.x. Remote attackers can distinguish valid usernames from invalid ones by measuring server response times.
A timing side-channel vulnerability in an FTP server that leaks whether usernames are valid based on response timing differences.
An FTP-server timing side channel that permits remote username enumeration from differing response times.
An FTP-server username-enumeration timing side channel.
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.