CVE-2020-11897 is a Ripple20 flaw in the IPv6 code of the Treck embedded TCP/IP stack: several malformed IPv6 packets from an unauthenticated attacker can trigger an out-of-bounds write on the device. NVD scores it 10.0 and lists Treck before 5.0.1.35, CERT/CC says to update to 6.0.1.67 or later, and Digi and Pepperl+Fuchs name affected devices.
Vulnerability summary
CVSS base score
10
Critical severity
EPSS score (FIRST)
9.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-11897 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Treck TCP/IP stack (IPv6) | cpe:2.3:a:treck:tcp\/ip:*:*:*:*:*:*:*:* | NVD: before 5.0.1.35; 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 lists this CVE) |
| Pepperl+Fuchs VDM100-50/150/300-EIP/G2 distance sensors | — | firmware 2.00 and earlier; mitigation only (CERT@VDE VDE-2021-028) |
What does this mean for affected devices?
CVE-2020-11897 is one of the 19 Ripple20 vulnerabilities in the Treck TCP/IP stack, disclosed on 2020-06-16. NVD records it as an out-of-bounds write (CWE-787) and 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; the CVE text reads "The Treck TCP/IP stack before 5.0.1.35 has an Out-of-Bounds Write via multiple malformed IPv6 packets" (NVD). CERT/CC's VU#257161 describes it as improper handling of a length parameter inconsistency (CWE-130) in the IPv6 component, where "an unauthorized network attacker can send a malicious packet that can lead to out of bounds write on the target device". CISA's ICSA-20-168-01 (CSAF) gives the same CVSS 10.0 and tells users to update Treck to 6.0.1.67 or later.
Which Treck versions and devices are affected?
The version line is lower than for most Ripple20 CVEs: NVD's CPE range ends before 5.0.1.35, while the other Ripple20 records mostly end before 6.0.1.66. A device that ships a 6.0.1.x Treck build may therefore be outside NVD's range for this CVE yet still affected by its siblings, so a scanner result for one Ripple20 CVE says nothing about the others. CERT/CC and CISA name one fix line for all 19: 6.0.1.67 or later.
Device vendors, not Treck, name the products. Digi's security notice lists this CVE and names 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 from the week of 2020-04-20. CERT@VDE's VDE-2021-028 lists CVE-2020-11897 for Pepperl+Fuchs VDM100-50, -150 and -300-EIP/G2 distance sensors with firmware 2.00 and earlier and gives network isolation as the mitigation. CERT/CC's vendor table for this CVE marks B. Braun, Baxter, Caterpillar, Eaton, HP Inc., Hewlett Packard Enterprise, Rockwell Automation, Schneider Electric and Xerox, among others, as affected. Cisco's Ripple20 advisory states that its StarOS software is not affected by this CVE, although StarOS is affected by other Ripple20 flaws.
Is CVE-2020-11897 exploited?
It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13); the only KEV-listed Ripple20 flaw is CVE-2020-11899, added on 2022-03-03. FIRST EPSS gives CVE-2020-11897 0.0937, the 95.5th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
What should device makers and operators do?
Find out whether the stack, SDK or module is Treck-derived, get the 6.0.1.67-or-later code or the module vendor's fixed firmware, and rebuild. IPv6-only exposure matters here: an IPv4-only build with IPv6 compiled out has no path to this bug, which is the kind of feature-gate decision our embedded TCP/IP stack vulnerabilities guide walks through. Our memory corruption fix guide covers the length-check pattern behind the fix. The other Ripple20 pages are CVE-2020-11896 (IPv4 tunneling), CVE-2020-11898 (IPv4/ICMPv4 leak) and CVE-2020-11901 (DNS resolver).
Evidence
- Treck TCP/IP before 5.0.1.35 has an out-of-bounds write via multiple malformed IPv6 packets; NVD CVSS v3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), CWE-787. — NVD
- CWE-130 length parameter inconsistency in the IPv6 component; out-of-bounds write; update to 6.0.1.67 or later; vendor table marks B. Braun, Baxter, Caterpillar, Eaton, HP Inc., HPE, Rockwell Automation, Schneider Electric, Xerox and others as affected. — CERT/CC VU#257161
- CISA: CVSS 10.0, out-of-bounds write in the IPv6 component; update Treck to 6.0.1.67 or later. — CISA ICSA-20-168-01 (CSAF)
- Digi lists CVE-2020-11897 and its Connect/ConnectPort/AnywhereUSB/NetSilicon/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 by CVE-2020-11897; mitigation is network isolation. — CERT@VDE VDE-2021-028
- Cisco StarOS software is not affected by CVE-2020-11897. — Cisco Security Advisory cisco-sa-treck-ip-stack-JyBQ5GyC
- 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.09365 (95.5th percentile), dataset 2026-11-16. — FIRST EPSS

Related advisories
Sources
- NVD
- CERT/CC VU#257161: Treck IP stacks contain multiple vulnerabilities
- CISA ICSA-20-168-01: Treck TCP/IP (CSAF)
- Digi International security notice: Treck TCP/IP stack Ripple20
- CERT@VDE VDE-2021-028: Pepperl+Fuchs VDM100 EIP/G2
- Cisco Security Advisory: Treck IP Stack Vulnerabilities (Ripple20)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which Treck versions are affected by CVE-2020-11897?
The CVE text and NVD's CPE range say Treck TCP/IP before 5.0.1.35, an earlier cut-off than most Ripple20 CVEs. CERT/CC and CISA tell users to update to 6.0.1.67 or later, which covers all 19 Ripple20 flaws (per NVD, CERT/CC VU#257161 and CISA ICSA-20-168-01).
Which devices are affected by CVE-2020-11897?
Digi lists this CVE for its Connect and ConnectPort modules, AnywhereUSB and NET+OS 7.x products, and CERT@VDE lists it for Pepperl+Fuchs VDM100 EIP/G2 sensors with firmware 2.00 and earlier. Cisco says its StarOS software is not affected by this one (per Digi, VDE-2021-028 and Cisco).
Is CVE-2020-11897 in the CISA KEV catalog?
No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0937, the 95.5th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Does an IPv4-only build need the fix?
The flaw sits in Treck's IPv6 component and is reached through malformed IPv6 packets, so a build with IPv6 compiled out has no path to it; record that build flag as evidence in a not-affected statement, and still update for the IPv4 Ripple20 flaws (per CERT/CC VU#257161 and NVD).
Questions about this page?