Serv-U FTP server 4.x and 5.x allows remote attackers to cause a denial of service (application crash) via a STORE UNIQUE (STOU) command with an MS-DOS device name argument such as (1) COM1, (2) LPT1, (3) PRN, or (4) AUX.
CVE-2004-1675
NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 12%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 95.8%
- KEV
- Not listed
Published
September 11, 2004
Last Modified
June 16, 2026
References (8)
- cve@mitrehttp://marc.info/?l=bugtraq&m=109495074211638&w=2
- cve@mitrehttp://secunia.com/advisories/12507/
- cve@mitrehttp://www.securityfocus.com/bid/11155
- cve@mitrehttps://exchange.xforce.ibmcloud.com/vulnerabilities/17329
- af854a3a-2127-422b-91ae-364da2661108http://marc.info/?l=bugtraq&m=109495074211638&w=2
- af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/12507/
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/11155
- af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/17329
Frequently asked(4)
What is CVE-2004-1675?
CVE-2004-1675 is a none vulnerability published on September 11, 2004. Serv-U FTP server 4.x and 5.x allows remote attackers to cause a denial of service (application crash) via a STORE UNIQUE (STOU) command with an MS-DOS device name argument such as (1) COM1, (2) LPT1, (3) PRN, or (4) AUX.
When was CVE-2004-1675 disclosed?
CVE-2004-1675 was first published in the National Vulnerability Database on September 11, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-1675 actively exploited?
CVE-2004-1675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2004-1675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2004-1675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2004-1675
Is Your Infrastructure Affected by CVE-2004-1675?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.