Skip to content
Fencer Vulns
medium 5.3

CVE-2020-10136 json

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

published 2020-06-02 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-2599

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
28.5%
EPSS 28.5% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • treck tcp/ip 6.0.1.67
  • digi saros 8.1.0.1
  • hp x3220nr_firmware 3.00.11.08

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10136 updated cvss 7.5

kernel: IP-in-IP protocol routes arbitrary traffic by default

  • Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, kernel-alt, python-perf, +9 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise MRG 2 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

28.54% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • IETF RFC2003 - IP Encapsulation within IP

Classification

Weakness
  • CWE-290 Authentication Bypass by Spoofing

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.