CVE-2020-11896 is the most severe Ripple20 flaw: a length-handling bug in the IPv4 tunneling code of the Treck embedded TCP/IP stack that lets an unauthenticated attacker run code on a device with crafted packets. NVD scores it 10.0, CERT/CC says to update Treck to 6.0.1.67 or later, and Digi, Pepperl+Fuchs and Siemens list affected devices.
Vulnerability summary
CVSS base score
10
Critical severity
EPSS score (FIRST)
36.9%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-11896 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Treck TCP/IP stack | cpe:2.3:a:treck:tcp\/ip:*:*:*:*:*:*:*:* | NVD: before 6.0.1.66; CERT/CC VU#257161 and CISA ICSA-20-168-01: update to 6.0.1.67 or later |
| Digi Connect ME/EM/ES/SP/WME, Connect 9C/9P, ConnectPort X2/X4/TS, AnywhereUSB and NET+OS 7.x products | — | firmware before the releases of the week of 2020-04-20 (Digi security notice) |
| Pepperl+Fuchs VDM100-50/150/300-EIP/G2 distance sensors | — | firmware 2.00 and earlier (CERT@VDE VDE-2021-028) |
| Siemens SIMATIC RTLS Gateway RTLS4030G and RTLS4430G | — | all versions; vendor lists no fix (CISA ICSA-24-046-03) |
What does this mean for affected devices?
CVE-2020-11896 is one of the 19 Ripple20 vulnerabilities that JSOF researchers Moshe Kol and Shlomi Oberman reported in the Treck TCP/IP stack, disclosed on 2020-06-16. CERT/CC's VU#257161 says the Treck stack "contains multiple vulnerabilities, most of which are caused by memory management bugs", and that a remote, unauthenticated attacker "may be able to use specially-crafted network packets to cause a denial of service, disclose information, or execute arbitrary code". CISA's ICSA-20-168-01 (CSAF) describes this CVE as "improper handling of length parameter inconsistency in IPv4/UDP component" (CWE-130) that "may result in remote code execution".
NVD scores it 10.0 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H and weaknesses CWE-119 and CWE-787 (NVD). The version numbers differ by source: the CVE text and NVD's CPE range say "before 6.0.1.66", while CERT/CC and CISA tell users to update to 6.0.1.67 or later. CERT/CC's example detection rule for this CVE and CVE-2020-11900 alerts on fragments inside an IP-in-IP tunnel, which shows the packet path involved.
Treck is licensed to device makers and often rebranded, so the reliable source is the device vendor. Digi's security notice lists Connect ME, EM, ES, SP and WME modules, Connect 9C and 9P, ConnectPort X2 (not X2e), X4 and TS (not LTS), AnywhereUSB (not Plus), NetSilicon processors and "any embedded products using the NET+OS 7.X environments", with fixed firmware released in the week of 2020-04-20. Those modules end up inside other products: CERT@VDE's VDE-2021-028 lists Pepperl+Fuchs VDM100-50, -150 and -300-EIP/G2 distance sensors with firmware 2.00 and earlier, citing the Digi notice, and says an affected sensor may drop its cyclic connections or disappear from the network. In 2024 CISA's ICSA-24-046-03 (CSAF) added Siemens SIMATIC RTLS4030G and RTLS4430G gateways, all versions, with a CVSS score of 7.5; Siemens lists no fix and points to the security recommendations in the product manual.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13); its Ripple20 sibling CVE-2020-11899 is, added on 2022-03-03. FIRST EPSS gives CVE-2020-11896 0.3685, the 98.5th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
Device makers should find out whether their stack, SDK or module is Treck-derived, get the 6.0.1.67-or-later code or the module vendor's firmware, and rebuild. Until devices are updated, CERT/CC recommends blocking IP-in-IP tunneling and IP fragments where unused. Our embedded TCP/IP stack vulnerabilities guide covers identifying a rebranded stack in an image, our memory corruption fix guide covers the bug class, and the DNS resolver flaw from the same set is CVE-2020-11901.
Evidence
- Ripple20: Treck stack has multiple memory-management vulnerabilities; remote unauthenticated attacker may cause DoS, info disclosure or code execution; update to 6.0.1.67 or later; example rule for IP-in-IP fragments names CVE-2020-11896 and CVE-2020-11900. — CERT/CC VU#257161
- CISA: improper handling of length parameter inconsistency in IPv4/UDP component (CWE-130), may result in RCE; update Treck to 6.0.1.67 or later. — CISA ICSA-20-168-01 (CSAF)
- NVD CVSS v3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), CWE-119 and CWE-787; CPE range before 6.0.1.66. — NVD
- Digi lists Connect ME/EM/ES/SP/WME, Connect 9C/9P, ConnectPort X2/X4/TS, AnywhereUSB, NetSilicon and NET+OS 7.x products; fixed firmware released week of 2020-04-20. — Digi International security notice
- Pepperl+Fuchs VDM100-50/150/300-EIP/G2 firmware <= 2.00 affected via the Digi Treck stack. — CERT@VDE VDE-2021-028
- Siemens SIMATIC RTLS4030G and RTLS4430G gateways, all versions, CVSS 7.5, no fix listed. — CISA ICSA-24-046-03 (CSAF)
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13); CVE-2020-11899 added 2022-03-03. — CISA KEV
- EPSS 0.36852 (98.5th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Treck version fixes CVE-2020-11896?
CERT/CC and CISA tell users to update to Treck TCP/IP 6.0.1.67 or later and to contact Treck for patches. The CVE text and NVD range say versions before 6.0.1.66 are affected, so the two sources differ by one build (per CERT/CC VU#257161, CISA ICSA-20-168-01 and NVD).
Which devices are affected by CVE-2020-11896?
Vendors name them, not Treck. Digi lists its Connect and ConnectPort modules, AnywhereUSB and NET+OS 7.x products; CERT@VDE lists Pepperl+Fuchs VDM100 EIP/G2 sensors with firmware 2.00 and earlier; CISA lists Siemens SIMATIC RTLS4030G and RTLS4430G gateways, all versions (per Digi, VDE-2021-028 and ICSA-24-046-03).
Is CVE-2020-11896 in the CISA KEV catalog?
No, not as of 2026-11-16 (catalog version 2026.11.13), although the related Ripple20 flaw CVE-2020-11899 was added on 2022-03-03. FIRST EPSS gives CVE-2020-11896 0.3685, the 98.5th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
How can a network reduce exposure before firmware is updated?
CERT/CC recommends normalising or rejecting IP fragments, blocking IP-in-IP and IPv6-in-IPv4 tunneling where it is not used, and its example detection rule alerts on fragments inside an IP-in-IP tunnel, the path this CVE uses (per CERT/CC VU#257161).
Questions about this page?