CVE-2005-2767 json
Buffer overflow in LeapFTP allows remote attackers to execute arbitrary code via a long Host string in a Site Queue (.lsq) file.
published 2005-09-02 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2768
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.9%
- EPSS 6.9% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in LeapFTP allows remote attackers to execute arbitrary code via a long Host string in a Site Queue (.lsq) file.
Patch / fix
- securityfocus.com/bid/14655 patch
- leapware.com/security/2005082301.txt advisory
- secway.org/advisory/AD20050824.txt advisory
- secunia.com/advisories/16552/ advisory
Timeline
- First public exploit (EDB-26194)
- Published
Exploit prediction
6.92% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26194 LeapFTP Client 2.7.3/2.7.4 - '.LSQ' File Remote Buffer Overflow (PoC) dos, 2005-08-24
- securityfocus.com http://www.securityfocus.com/bid/14655 referenced PoC, tagged "exploit" by a source, unverified
- leapware.com http://www.leapware.com/security/2005082301.txt referenced PoC, tagged "exploit" by a source, unverified
- secway.org http://secway.org/advisory/AD20050824.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
securityfocus.com
/bid/14655
vdb-entry, exploit, patch
-
leapware.com
/security/2005082301.txt
exploit, patch, vendor-advisory
-
secway.org
/advisory/AD20050824.txt
exploit, patch, vendor-advisory
-
secunia.com
/advisories/16552/
third-party-advisory, patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/21974
vdb-entry
-
marc.info
/?l=bugtraq&m=112491089723070&w=2
mailing-list
-
securitytracker.com
/id?1014785
vdb-entry
Sources
- CVE List CVE-2005-2767
- NVD CVE-2005-2767
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.