Summary
Critical vulnerabilities have been discovered in the utilized component TRECK TCP/IP Stack by Digi International Inc.
For more information see advisory by Digi International Inc.:
Digi International Security Notice - TRECK TCP/IP Stack "RIPPLE20" VU#257161 ICS-VU-035787 | Digi International
Details
Impact
Pepperl+Fuchs analyzed and identified affected devices.
The impact on the affected device is that it can
- no longer perform acyclic requests
- may drop all established cyclic connections may
- disappear completely from the network
Mitigation
An external protective measure is required.
- Minimize network exposure for affected products and ensure that they are not accessible via the Internet.
- Isolate affected products from the corporate network.
- If remote access is required, use secure methods such as virtual private networks (VPNs).
Vulnerabilities 19
-
Medium 5.4
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.
KEV Mar 3, 2022 -
Critical 9.8CVE-2020-11910 EPSS 11%
The Treck TCP/IP stack before 6.0.1.66 has an ICMPv4 Out-of-bounds Read.
-
Critical 9.1
The Treck TCP/IP stack before 6.0.1.66 has an IPv4 Integer Underflow.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.
-
Unscored —
The Treck TCP/IP stack before 5.0.1.35 has an Out-of-Bounds Write via multiple malformed IPv6 packets.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 improperly handles an IPv4/ICMPv4 Length Parameter Inconsistency, which might al…
-
Unscored —CVE-2020-11900 EPSS 13%
The Treck TCP/IP stack before 6.0.1.41 has an IPv4 tunneling Double Free.
-
Unscored —CVE-2020-11901 EPSS 22%
The Treck TCP/IP stack before 6.0.1.66 allows Remote Code execution via a single invalid DNS response.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.28 has a DHCP Out-of-bounds Read.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has an Integer Overflow during Memory Allocation that causes an Out-of-Bounds Wr…
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has a DHCPv6 Out-of-bounds Read.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has an Ethernet Link Layer Integer Underflow.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP.
-
Unscored —
The Treck TCP/IP stack before 4.7.1.27 mishandles '\0' termination in DHCP.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has Improper ICMPv4 Access Control.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has a TCP Out-of-bounds Read.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.
-
Unscored —
The Treck TCP/IP stack before 6.0.1.66 has an ARP Out-of-bounds Read.
Revision history
-
#2
Fix: added distribution
-
#1
Initial revision.
References
-
Pepperl+Fuchs advisory overview at CERT@VDE
https://certvde.com/de/advisories/vendor/pepperl+fuchs/
-
VDE-2021-028: Pepperl+Fuchs: Multiple VDM100-Distance Ethernet-IP sensors with multiple vulnerabilities - HTML
https://certvde.com/en/advisories/VDE-2021-028