Skip to content
Fencer Vulns
critical 9.3

CVE-2009-1759 in the critical feed json

Stack-based buffer overflow in the btFiles::BuildFromMI function (trunk/btfiles.cpp) in Enhanced CTorrent (aka dTorrent) 3.3.2 and probably…

published 2009-05-22 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1754

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

Summary

Stack-based buffer overflow in the btFiles::BuildFromMI function (trunk/btfiles.cpp) in Enhanced CTorrent (aka dTorrent) 3.3.2 and probably earlier, and CTorrent 1.3.4, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Torrent file containing a long path.

Patch / fix

  • ctorrent Debian 14, Debian 13, Debian 12 1.3.4-dnh3.2-1.1

debian advisories DEBIAN-CVE-2009-1759

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-2009-1759 updated

ctorrent: stack-based buffer overflow vulnerability

  • 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-8470)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-8470 cTorrent/DTorrent - '.torrent' Local Buffer Overflow local, 2009-04-17
  • securityfocus.com http://www.securityfocus.com/bid/34584 referenced PoC, tagged "exploit" by a source, unverified

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

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.