LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10136: IP-in-IP protocol allows a remote, unauthenticated attacker to route arbitrary network traffic

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects how IP-in-IP tunneling can be handled. If a system accepts tunneled packets without validating them first, an unauthenticated remote party may bypass network controls or cause traffic to be routed unexpectedly. The source bundle does not provide CVSS or broad product-specific impact details.

Executive priority

Treat this as a network exposure review priority, especially for perimeter and routing infrastructure. Urgency rises if IP-in-IP is enabled on internet-facing systems or unsupported devices.

Technical view

CVE-2020-10136 describes improper validation during IP-in-IP decapsulation and routing under RFC 2003, mapped to CWE-290. The risk is spoofing, access-control bypass, and unexpected forwarding when devices decapsulate untrusted IP-in-IP traffic. Confirm exposure by implementation and vendor behavior, not by the RFC alone.

Likely exposure

Organizations are most likely exposed through routers, firewalls, switches, gateways, or embedded devices that accept IP-in-IP traffic from untrusted networks. Exposure depends on product implementation and configuration.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. The issue is remotely reachable and unauthenticated where IP-in-IP decapsulation is exposed, but exploit status and product coverage are incomplete in the provided sources.

Researcher notes

The CVE is protocol-oriented and the affected implementation set is not fully described in the bundle. Avoid assuming all RFC 2003 implementations are affected; validate actual decapsulation behavior and vendor advisories.

Mitigation direction

  • Check vendor advisories for affected products and fixed versions.
  • Disable IP-in-IP tunneling where it is not required.
  • Restrict tunnel decapsulation to trusted peers and interfaces.
  • Filter unexpected IP-in-IP traffic at network boundaries.
  • Review Cisco and Digi guidance if their products are deployed.

Validation and detection

  • Inventory devices that support RFC 2003 or IP-in-IP tunneling.
  • Review configurations for exposed decapsulation on internet-facing interfaces.
  • Confirm whether vendors identify deployed versions as affected.
  • Check perimeter telemetry for unexpected IP-in-IP traffic patterns.
  • Document any required tunnels and their trusted endpoints.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-290: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IETFRFC2003 - IP Encapsulation within IPSTD 1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.