# CVE-2009-1759: Memory corruption in n/a

> Remote attackers can cause a crash or execute arbitrary code by tricking a user into opening a malicious Torrent file with a long path.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1759, DSA-1817-1, GHSA-chfx-pv5j-438m

## What is CVE-2009-1759?

CVE-2009-1759 is a critical memory corruption vulnerability in n/a, published on 22 May 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-1759?

It affects 2 products.


Products: Rahul Ctorrent, Rahul Dtorrent.

## How do I fix CVE-2009-1759?

Apply the vendor's patch.

## Is CVE-2009-1759 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1759 exists.

Public exploit code:

- cTorrent/DTorrent - '.torrent' Local Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1759 and fix it if it is affected.

What it is: CVE-2009-1759 is a critical memory corruption vulnerability in n/a, published on 22 May 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1759 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-1759/ (Markdown: https://insights.sbomify.com/CVE-2009-1759/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-1759
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-1759
- OSV: https://osv.dev/vulnerability/CVE-2009-1759

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-1759/
Summaries are generated and may contain mistakes; the official description above is the record.