CVE-2006-6858

Miredo 0.9.8 through 1.0.5 does not properly authenticate a Teredo bubble during UDP hole punching with HMAC-MD5-64 hashing, which allows remote attackers to impersonate an arbitrary Teredo client...

CVE-2006-6858

Miredo 0.9.8 through 1.0.5 does not properly authenticate a Teredo bubble during UDP hole punching with HMAC-MD5-64 hashing, which allows remote attackers to impersonate an arbitrary Teredo client...

Teredo Server Detection

The remote host is running a Teredo server. Teredo is a protocol for tunneling IPv6 over UDP, and is used to give nodes the ability to obtain IPv6 connectivity behind IPv4 network address translation NAT devices. A Teredo server is a node that is connected to both IPv4 and IPv6 networks. C Tenabl...

Teredo IPv6 Client Detection

Binary data 3875.prm...

Security Advisory 0604

Security Advisory 0604 Summary : Input Validation error in Teredo tunnel Date : 31 December 2006 Affected versions : Miredo 1.0.5 down to 0.9.8 ID : MTFL-SA-0604 Details Authentication of a Teredo bubble as part of UDP hope punching with HMAC-MD5-64 hashing is done improperly and can easily be...

Teredo Server Detection

Binary data 3876.prm...

DEBIAN-CVE-2006-6858

Miredo 0.9.8 through 1.0.5 does not properly authenticate a Teredo bubble during UDP hole punching with HMAC-MD5-64 hashing, which allows remote attackers to impersonate an arbitrary Teredo client...

CVE-2006-6858

Miredo 0.9.8 through 1.0.5 does not properly authenticate a Teredo bubble during UDP hole punching with HMAC-MD5-64 hashing, which allows remote attackers to impersonate an arbitrary Teredo client...

CVE-2006-6858

Miredo 0.9.8 through 1.0.5 does not properly authenticate a Teredo bubble during UDP hole punching with HMAC-MD5-64 hashing, which allows remote attackers to impersonate an arbitrary Teredo client...

CVE-2006-6264

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

CVE-2006-6263

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

CVE-2006-6265

Teredo clients, when located behind a restricted NAT, allow remote attackers to establish an inbound connection without the guessing required to find a port mapping for a traditional restricted NAT client, by 1 using the client port number contained in the Teredo address or 2 following the...

CVE-2006-6266

Teredo clients, when following item 6 of RFC4380 section 5.2.3, start direct IPv6 connectivity tests aka ping tests in response to packets from non-Teredo source addresses, which might allow remote attackers to induce Teredo clients to send packets to third parties...

CVE-2006-6264

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

CVE-2006-6266

Teredo clients, when following item 6 of RFC4380 section 5.2.3, start direct IPv6 connectivity tests aka ping tests in response to packets from non-Teredo source addresses, which might allow remote attackers to induce Teredo clients to send packets to third parties...

CVE-2006-6263

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

CVE-2006-6265

Teredo clients, when located behind a restricted NAT, allow remote attackers to establish an inbound connection without the guessing required to find a port mapping for a traditional restricted NAT client, by 1 using the client port number contained in the Teredo address or 2 following the...

CVE-2006-6266

Teredo clients, when following item 6 of RFC4380 section 5.2.3, start direct IPv6 connectivity tests aka ping tests in response to packets from non-Teredo source addresses, which might allow remote attackers to induce Teredo clients to send packets to third parties...

CVE-2006-6265

Teredo clients, when located behind a restricted NAT, allow remote attackers to establish an inbound connection without the guessing required to find a port mapping for a traditional restricted NAT client, by 1 using the client port number contained in the Teredo address or 2 following the...

CVE-2006-6264

CVE-2006-6264 describes a Teredo weakness where trusted peer entries are created for arbitrary incoming Teredo addresses, even when the low 32 bits encode an intranet address. This could allow remote attackers to send IPv4 traffic to intranet hosts that use non-RFC1918 addresses, bypassing IPv4 i...