CVE-2005-0277 json
Buffer overflow in the FTP service in 3Com 3CDaemon 2.0 revision 10 allows remote attackers to cause a denial of service (application crash…
published 2005-02-10 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0278
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 61.9%
- EPSS 61.9% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 4
- Metasploit, Exploit-DB
Summary
Buffer overflow in the FTP service in 3Com 3CDaemon 2.0 revision 10 allows remote attackers to cause a denial of service (application crash) and execute arbitrary code via (1) a long username in the USER command or (2) an FTP command that contains a long argument, such as cd, send, or ls.
Timeline
- First public exploit (Metasploit exploit/windows/ftp/3cdaemon_ftp_user)
- Published
Exploit prediction
61.91% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/ftp/3cdaemon_ftp_user 3Com 3CDaemon 2.0 FTP Username Overflow metasploit exploit, average rank, 2005-01-04
- EDB-16730 3Com 3CDaemon 2.0 FTP Server - 'Username' Remote Overflow (Metasploit) remote, 2010-09-20
- EDB-827 3Com 3CDaemon FTP - Unauthorized 'USER' Remote Buffer Overflow remote, 2005-02-18
- EDB-825 3Com FTP Server 2.0 - Remote Overflow remote, 2005-02-17
- securityfocus.com http://www.securityfocus.com/bid/12155 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
securityfocus.com
/bid/12155
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/18754
vdb-entry
-
marc.info
/?l=bugtraq&m=110485674622696&w=2
mailing-list
-
marc.info
/?l=bugtraq&m=110886719528518&w=2
mailing-list
Sources
- CVE List CVE-2005-0277
- NVD CVE-2005-0277
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.