# CVE-2006-3417: Security feature bypass in n/a

> Tor clients may prefer less trustworthy entry nodes over designated guards, allowing attackers to bypass security protections and monitor traffic.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2006
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2006-3417, GHSA-5p7x-732m-p6x3

## What is CVE-2006-3417?

CVE-2006-3417 is a medium-severity vulnerability in Tor Tor, published on 7 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tor client before 0.1.1.20 prefers entry points based on is_fast or is_stable flags, which could allow remote attackers to be preferred over nodes that are identified as more trustworthy "entry guard" (is_guard) systems by directory authorities.

## Which versions are affected by CVE-2006-3417?

It affects 1 product.


Products: Tor Tor.

## How do I fix CVE-2006-3417?

Upgrade to a fixed version.

## Is CVE-2006-3417 being exploited?

There is no known exploitation of CVE-2006-3417 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-2009-0414](https://insights.sbomify.com/CVE-2009-0414/): Memory corruption in n/a (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3417 and fix it if it is affected.

What it is: CVE-2006-3417 is a medium-severity vulnerability in Tor Tor, published on 7 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3417 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-2006-3417/ (Markdown: https://insights.sbomify.com/CVE-2006-3417/index.md)
```

## Sources

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

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