Treck Inc. has a new version to handle multiple vulnerabilities in its TCP/IP stack, according to an updated report from CISA.

The vulnerabilities are an improper handling of length parameter inconsistency, improper input validation, double free, out-of-bounds read, integer overflow or wraparound, improper null termination, and improper access control.

There is a public report, known as “Ripple20,” that details vulnerabilities found in the Treck TCP/IP stack. CISA released an advisory to provide early notice of the vulnerabilities and identify baseline mitigations for reducing risks to these and other potential attacks.

Successful exploitation of these remotely exploitable vulnerabilities, discovered by Shlomi Oberman and Moshe Kol from JSOF, may allow remote code execution or exposure of sensitive information.

Schneider Bold

The Treck TCP/IP stack is affected including:

  • IPv4
  • IPv6
  • UDP
  • DNS
  • DHCP
  • TCP
  • ICMPv4
  • ARP

In one vulnerability, there is an improper handling of length parameter inconsistency in IPv4/UDP component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in remote code execution.

CVE-2020-11896 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 10.0.

In addition, there is an improper handling of length parameter inconsistency in IPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in possible out-of-bounds write.

CVE-2020-11897 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 10.0.

Also, there is an improper handling of length parameter inconsistency in IPv4/ICMPv4 component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in out-of-bounds read.

CVE-2020-11898 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.1.

In another issue, there is an improper input validation in IPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds read and a possible denial of service.

CVE-2020-11899 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.4.

In addition, there is a possible double free in IPv4 tunneling component when handling a packet sent by a network attacker. This vulnerability may result in use after free.

CVE-2020-11900 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 8.2.

Also, there is an improper input validation in DNS resolver component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in remote code execution.

CVE-2020-11901 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.0.

In another issue, there is an improper input validation in IPv6 over IPv4 tunneling component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds read.

CVE-2020-11902 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.3.

In addition, there is a possible out-of-bounds read in DHCP component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow exposure of sensitive information.

CVE-2020-11903 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.

Also, there is a possible integer overflow or wraparound in memory allocation component when handling a packet sent by an unauthorized network attacker may result in out-of-bounds write.

CVE-2020-11904 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.6.

In another vulnerability, there is a possible out-of-bounds read in DHCPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow exposure of sensitive information.

CVE-2020-11905 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.

In addition, there is an improper input validation CWE-20 in Ethernet link layer component from a packet sent by an unauthorized user.

CVE-2020-11906 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.0.

Also, there is an improper handling of length parameter inconsistency in TCP component, from a packet sent by an unauthorized network attacker.

CVE-2020-11907 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.0.

In another hole, there is an improper null termination in DHCP component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow exposure of sensitive information.

CVE-2020-11908 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.1.

In addition, there is an improper input validation in IPv4 component when handling a packet sent by an unauthorized network attacker.

CVE-2020-11909 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.

Also, there is an improper input validation in ICMPv4 component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds Read.

CVE-2020-11910 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.

In another issue, the affected product is vulnerable to improper access control, which may allow an attacker to change one specific configuration value.

CVE-2020-11911 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.

There is also an improper input validation in TCP component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds read.

CVE-2020-11912 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.

In addition, there is an improper input validation in IPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds Read.

CVE-2020-11913 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.

In another issue, there is an improper input validation in ARP component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow out-of-bounds read.

CVE-2020-11914 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.1.

The product sees use in the critical manufacturing, information technology, healthcare and public health, and transportation systems sectors. It also sees action on a global basis.

An attacker would need a high skill level to exploit. No known public exploits specifically target these vulnerabilities.

Treck recommends users apply the latest version of the affected products (Treck TCP/IP 6.0.1.66 or later versions). To obtain patches, click here to send an email.

For more detailed information on the vulnerabilities and the mitigating controls, click on the Treck advisory. Additional vendors affected by the reported vulnerabilities have also released security advisories related to their affected products.

Those advisories are as follows:

Pin It on Pinterest

Share This