CVE-2020-10136CWE-290

CVE-2020-10136: vulnerability in IETF RFC2003 - IP Encapsulation within IP

IP-in-IP protocol allows a remote, unauthenticated attacker to route arbitrary network traffic

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

8Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 29%
In short

The IP-in-IP protocol (RFC 2003) lacks proper validation of packets before processing them, allowing attackers to spoof traffic or bypass security controls by sending specially crafted encapsulated packets over the network.

Technical detail

The IP-in-IP encapsulation mechanism fails to validate source addresses and packet authenticity before decapsulation and routing, enabling remote unauthenticated attackers to perform IP spoofing attacks, circumvent access controls, and inject arbitrary traffic into the network routing path.

Summary generated and translated by AI from the official description.
IP-in-IP protocol specifies IP Encapsulation within IP standard (RFC 2003, STD 1) that decapsulate and route IP-in-IP traffic is vulnerable to spoofing, access-control bypass and other unexpected behavior due to the lack of validation to verify network packets before decapsulation and routing.