CVE-2004-2418 json
Buffer overflow in SlimFTPd 3.15 and earlier allows local users to execute arbitrary code via a long command, such as (1) CWD, (2) STOR, (3…
published 2004-12-31 21 y ago modified 2026-06-16 4 mo ago also EUVD-2004-2409
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in SlimFTPd 3.15 and earlier allows local users to execute arbitrary code via a long command, such as (1) CWD, (2) STOR, (3) MKD, and (4) STAT.
Patch / fix
- osvdb.org/11604 patch
- securitytracker.com/id?1012167 patch
- securityfocus.com/bid/11645 patch
- secunia.com/advisories/13161 advisory
Timeline
- First public exploit (EDB-623)
- Published
Exploit prediction
1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-623 SlimFTPd 3.15 - Remote Buffer Overflow remote, 2004-11-10
- securitytracker.com http://securitytracker.com/id?1012167 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2004-11/0293.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
secunia.com
/advisories/13161
third-party-advisory, patch, vendor-advisory
-
osvdb.org
/11604
vdb-entry, patch
-
securitytracker.com
/id?1012167
vdb-entry, exploit, patch
-
securityfocus.com
/bid/11645
vdb-entry, patch
-
archives.neohapsis.com
/archives/fulldisclosure/2004-11/0293.html
mailing-list, exploit
-
whitsoftdev.com
/slimftpd/
vendor-advisory, url-repurposed
-
exchange.xforce.ibmcloud.com
/vulnerabilities/18014
vdb-entry
Sources
- CVE List CVE-2004-2418
- NVD CVE-2004-2418
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.