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

> Remote attackers can bypass IPv4 ingress filtering to send traffic to intranet hosts via Teredo tunneling, affecting operating systems with Teredo enabled.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m2x3-pgjp-hpvv

## What is CVE-2006-6264?

CVE-2006-6264 is a high-severity vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Teredo creates trusted peer entries for arbitrary incoming source Teredo addresses, even if the low 32 bits represent an intranet address, which might allow remote attackers to send IPv4 traffic to intranet hosts that use non-RFC1918 addresses, bypassing IPv4 ingress filtering.

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

It affects 1 product.


Products: Microsoft Teredo.

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

No fix has been published for CVE-2006-6264 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-6264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6263](https://insights.sbomify.com/CVE-2006-6263/): Security feature bypass in n/a (medium 6.8)
- [CVE-2006-6266](https://insights.sbomify.com/CVE-2006-6266/): Server-side request forgery in n/a (medium 6.8)
- [CVE-2006-6265](https://insights.sbomify.com/CVE-2006-6265/): Security feature bypass in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6264 is a high-severity vulnerability in n/a, published on 4 Dec 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-6264 in the wild and no public exploit code.

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-2006-6264/ (Markdown: https://insights.sbomify.com/CVE-2006-6264/index.md)
```

## Sources

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

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