What is the severity of CVE-2006-6263?

CVE-2006-6263 is classified as a medium severity vulnerability.

How do I fix CVE-2006-6263?

To fix CVE-2006-6263, disable source routing on the Teredo client and ensure that proper security measures are in place on network gateways.

What causes CVE-2006-6263?

CVE-2006-6263 is caused by Teredo clients recognizing Routing headers in IPv6 packets when source routing is enabled.

Which software is affected by CVE-2006-6263?

CVE-2006-6263 affects Microsoft Teredo clients when source routing functionality is enabled.

What are the implications of CVE-2006-6263 on network security?

CVE-2006-6263 may allow remote attackers to bypass security policies on Internet gateways that drop source-routed packets.

Vulnerability/
CVE-2006-6263

medium

6.8

CWE

NVD-CWE-Other

4/12/2006

7/8/2024

CVE-2006-6263

First published: Mon Dec 04 2006(Updated: )

Teredo clients, when source routing is enabled, recognize a Routing header in an encapsulated IPv6 packet and send the packet to the next hop, which might allow remote attackers to bypass policies of certain Internet gateways that drop all source-routed packets.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Microsoft Teredo

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-6263?
CVE-2006-6263 is classified as a medium severity vulnerability.
How do I fix CVE-2006-6263?
To fix CVE-2006-6263, disable source routing on the Teredo client and ensure that proper security measures are in place on network gateways.
What causes CVE-2006-6263?
CVE-2006-6263 is caused by Teredo clients recognizing Routing headers in IPv6 packets when source routing is enabled.
Which software is affected by CVE-2006-6263?
CVE-2006-6263 affects Microsoft Teredo clients when source routing functionality is enabled.
What are the implications of CVE-2006-6263 on network security?
CVE-2006-6263 may allow remote attackers to bypass security policies on Internet gateways that drop source-routed packets.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/references
agent/author
agent/description
agent/first-publish-date
agent/tags
agent/event
agent/source
vendor/microsoft
canonical/microsoft teredo

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2006-6263?
CVE-2006-6263 is classified as a medium severity vulnerability.
How do I fix CVE-2006-6263?
To fix CVE-2006-6263, disable source routing on the Teredo client and ensure that proper security measures are in place on network gateways.
What causes CVE-2006-6263?
CVE-2006-6263 is caused by Teredo clients recognizing Routing headers in IPv6 packets when source routing is enabled.
Which software is affected by CVE-2006-6263?
CVE-2006-6263 affects Microsoft Teredo clients when source routing functionality is enabled.
What are the implications of CVE-2006-6263 on network security?
CVE-2006-6263 may allow remote attackers to bypass security policies on Internet gateways that drop source-routed packets.