Skip to content
Fencer Vulns
medium 5.0

CVE-2008-0364 json

Buffer overflow in (1) BitTorrent 6.0 and earlier; and (2) uTorrent 1.7.5 and earlier, and 1.8-alpha-7834 and earlier in the 1.8.x series;…

published 2008-01-18 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-0374

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.9%
EPSS 8.9% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Buffer overflow in (1) BitTorrent 6.0 and earlier; and (2) uTorrent 1.7.5 and earlier, and 1.8-alpha-7834 and earlier in the 1.8.x series; on Windows allows remote attackers to cause a denial of service (application crash) via a long Unicode string representing a client version identifier.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-0364 updated

Bittorent uses wcscpy() unsafely

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-31032)
  2. Published

Exploit prediction

8.89% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-31032 BitTorrent 6.0 / uTorrent 1.6/1.7 - Peers Window Remote Code Execution remote, 2008-01-16
  • securityfocus.com http://www.securityfocus.com/bid/27321 referenced PoC, tagged "exploit" by a source, unverified
  • aluigi.altervista.org http://aluigi.altervista.org/adv/ruttorrent-adv.txt 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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.