# CVE-2007-4099: Information disclosure in n/a

> Remote attackers controlling guard nodes can obtain sensitive information by exploiting Tor's guard node selection logic, potentially enabling further attacks.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4099, GHSA-hvww-3pcr-wpmj

## What is CVE-2007-4099?

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

### Official description

Tor before 0.1.2.15 can select a guard node beyond the first listed never-before-connected-to guard node, which allows remote attackers with control of certain guard nodes to obtain sensitive information and possibly leverage further attacks.

## Which versions are affected by CVE-2007-4099?

It affects 1 product.


Products: Tor Tor.

## How do I fix CVE-2007-4099?

Upgrade to a fixed version.

## Is CVE-2007-4099 being exploited?

There is no known exploitation of CVE-2007-4099 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-2007-4099 and fix it if it is affected.

What it is: CVE-2007-4099 is a medium-severity vulnerability in Tor Tor, published on 30 Jul 2007. 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-2007-4099 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-2007-4099/ (Markdown: https://insights.sbomify.com/CVE-2007-4099/index.md)
```

## Sources

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

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