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

> Remote attackers can trigger heap corruption in Tor, potentially leading to code execution or denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0414, GHSA-5qgm-hgjh-hj48

## What is CVE-2009-0414?

CVE-2009-0414 is a critical memory corruption vulnerability in Tor Tor, published on 3 Feb 2009. It can be exploited over the network.

### Official description

Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption.

Weakness: CWE-399

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

It affects 1 product.


Products: Tor Tor.

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

Upgrade to a fixed version.

## Is CVE-2009-0414 being exploited?

There is no known exploitation of CVE-2009-0414 in the wild and no public exploit code.

## Other vulnerabilities in Tor Tor

- [CVE-2010-1676](https://insights.sbomify.com/CVE-2010-1676/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0939](https://insights.sbomify.com/CVE-2009-0939/): Tor before 0.2.0.34 treats incomplete IPv4 addresses as valid, which has unknown impact and attack vectors related to "Spec conformance," as (critical 10.0)
- [CVE-2008-5398](https://insights.sbomify.com/CVE-2008-5398/): Information disclosure in n/a (critical 9.3)
- [CVE-2011-2778](https://insights.sbomify.com/CVE-2011-2778/): Memory corruption in n/a (high 7.6)
- [CVE-2006-3409](https://insights.sbomify.com/CVE-2006-3409/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0414 is a critical memory corruption vulnerability in Tor Tor, published on 3 Feb 2009. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2009-0414 in the wild and no public exploit code.

Affected product: Tor Tor. 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-0414/ (Markdown: https://insights.sbomify.com/CVE-2009-0414/index.md)
```

## Sources

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

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