# CVE-2006-4508: Denial of service in n/a

> Remote attackers operating Tor entry nodes can route arbitrary traffic through clients or cause denial of service via flooding.

- **Severity:** Medium 4.0 (`AV:N/AC:H/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:** 31 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4508, GHSA-48qc-hgg4-x87r

## What is CVE-2006-4508?

CVE-2006-4508 is a medium-severity denial of service vulnerability in Tor Tor, published on 31 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in (1) Tor 0.1.0.x before 0.1.0.18 and 0.1.1.x before 0.1.1.23, and (2) ScatterChat before 1.0.2, allows remote attackers operating a Tor entry node to route arbitrary Tor traffic through clients or cause a denial of service (flood) via unspecified vectors.

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

It affects 2 products.


Products: Scatterchat Scatterchat, Tor Tor.

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

Upgrade to a fixed version.

## Is CVE-2006-4508 being exploited?

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

## Other vulnerabilities in Tor Tor

- [CVE-2006-4021](https://insights.sbomify.com/CVE-2006-4021/): Weak cryptography in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4508 is a medium-severity denial of service vulnerability in Tor Tor, published on 31 Aug 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-4508 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-4508/ (Markdown: https://insights.sbomify.com/CVE-2006-4508/index.md)
```

## Sources

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

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