CVE-2008-4434 in the critical feed json
Stack-based buffer overflow in (1) uTorrent 1.7.7 build 8179 and earlier and (2) BitTorrent 6.0.3 build 8642 and earlier allows remote atta…
published 2008-10-03 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4415
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.0%
- EPSS 11.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in (1) uTorrent 1.7.7 build 8179 and earlier and (2) BitTorrent 6.0.3 build 8642 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long Created By field in a .torrent file.
Timeline
- Published
- First public exploit (EDB-6787)
Exploit prediction
10.97% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6787 BitTorrent 6.0.3 - '.torrent' Local Stack Buffer Overflow local, 2008-10-19
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/31441
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/31445
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1020664
vdb-entry
- lists.immunitysec.com /pipermail/dailydave/attachments/20080811/35d6194b/attachment-0001.pdf
-
vupen.com
/english/advisories/2008/2341
vdb-entry
-
vupen.com
/english/advisories/2008/2340
vdb-entry
- forum.utorrent.com /viewtopic.php?id=44003
-
securityfocus.com
/bid/30653
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44404
vdb-entry
-
seclists.org
/dailydave/2008/q3/0155.html
mailing-list
Sources
- CVE List CVE-2008-4434
- NVD CVE-2008-4434
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.