CVE-2005-1163 json
Multiple buffer overflows in Yager 5.24 and earlier allow remote attackers to execute arbitrary code via (1) a crafted nickname or (2) a pa…
published 2005-04-18 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1166
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.7%
- EPSS 12.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Multiple buffer overflows in Yager 5.24 and earlier allow remote attackers to execute arbitrary code via (1) a crafted nickname or (2) a packet with a large amount of data.
Timeline
- Published
- First public exploit (EDB-953)
Exploit prediction
12.74% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-953 Yager 5.24 - Remote Buffer Overflow remote, 2005-04-25
- securityfocus.com http://www.securityfocus.com/bid/13177 referenced PoC, tagged "exploit" by a source, unverified
- aluigi.altervista.org http://aluigi.altervista.org/adv/yagerbof-adv.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/13178 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
References
-
securityfocus.com
/bid/13177
vdb-entry, exploit
-
aluigi.altervista.org
/adv/yagerbof-adv.txt
exploit, vendor-advisory
-
securityfocus.com
/bid/13178
vdb-entry, exploit
-
secunia.com
/advisories/14967
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/20100
vdb-entry
-
marc.info
/?l=bugtraq&m=111352154820865&w=2
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/20101
vdb-entry
-
osvdb.org
/15508
vdb-entry
-
osvdb.org
/15507
vdb-entry
Sources
- CVE List CVE-2005-1163
- NVD CVE-2005-1163
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.