Security Advisory

CVE-2020-11901: Ripple20 Treck DNS Resolver RCE

Last updated:
  • CVE-2020-11901

CVE-2020-11901 is a Ripple20 flaw in the DNS resolver of the Treck embedded TCP/IP stack: a single invalid DNS response can run code on the device, so an attacker who can answer its DNS queries needs no other access. NVD scores it 9.0, the fix is Treck 6.0.1.67 or later, and Digi and Pepperl+Fuchs list affected devices.

Vulnerability summary

CVSS base score

9

Critical severity

EPSS score (FIRST)

21.6%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-11901 · Source: NVD

Affected components

ComponentCPEVersion range
Treck TCP/IP stack (DNS resolver)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)

What does this mean for affected devices?

CVE-2020-11901 is one of the Ripple20 vulnerabilities in the Treck TCP/IP stack, disclosed through CERT/CC's VU#257161 on 2020-06-16. The CVE text reads "The Treck TCP/IP stack before 6.0.1.66 allows Remote Code execution via a single invalid DNS response", and CISA's ICSA-20-168-01 (CSAF) places it in the "DNS resolver component", as improper input validation (CWE-20) that "may result in remote code execution". CERT/CC and CISA both tell users to update to Treck 6.0.1.67 or later and to contact Treck for patches.

NVD scores it 9.0 with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H and lists CWE-125, CWE-131, CWE-330 and CWE-787 (NVD). The high attack complexity reflects the delivery path: the attacker has to get a malicious answer to a DNS query the device sends, by sitting on the path, controlling a resolver it uses or racing the real answer. A device that never resolves names through the Treck resolver is not exposed through this CVE.

That makes the build configuration part of the answer. CERT/CC's vendor list records Aruba Networks as affected by CVE-2020-11896 but not by CVE-2020-11901, while vendors such as Digi, Baxter, B. Braun, Caterpillar, Eaton, Rockwell Automation and Schneider Electric are marked affected by both. 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) and products built on NET+OS 7.x, with fixed firmware from the week of 2020-04-20. CERT@VDE's VDE-2021-028 lists Pepperl+Fuchs VDM100-50, -150 and -300-EIP/G2 sensors with firmware 2.00 and earlier, which use the Digi Treck stack, and names this CVE among the 19.

The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.2161, the 97.7th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

Device makers should check with their stack, SDK or module supplier whether the Treck DNS resolver is compiled in, take Treck 6.0.1.67 or later or the module vendor's firmware, and rebuild. On the network side CERT/CC recommends that operators "normalize DNS through a secure recursive server or application layer firewall", so devices only receive well-formed answers from a trusted resolver. Our embedded TCP/IP stack vulnerabilities guide covers finding the stack in an image, our memory corruption fix guide covers the bug class, and the IPv4 tunneling flaw from the same set is CVE-2020-11896.

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • Ripple20 disclosed 2020-06-16; update to Treck 6.0.1.67 or later; vendor list marks Aruba affected by CVE-2020-11896 but not CVE-2020-11901; recommends normalizing DNS through a secure recursive server or application layer firewall. — CERT/CC VU#257161
  • CISA: improper input validation (CWE-20) in DNS resolver component, may result in RCE. — CISA ICSA-20-168-01 (CSAF)
  • NVD CVSS v3.1 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H); CWE-125, CWE-131, CWE-330, CWE-787; before 6.0.1.66. — NVD
  • Digi lists affected Connect/ConnectPort/AnywhereUSB/NET+OS 7.x products; fixed firmware week of 2020-04-20. — Digi International security notice
  • Pepperl+Fuchs VDM100 EIP/G2 firmware <= 2.00 affected; CVE-2020-11901 listed. — CERT@VDE VDE-2021-028
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.21607 (97.7th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT/CC VU#257161: Treck IP stacks contain multiple vulnerabilities
  3. CISA ICSA-20-168-01: Treck TCP/IP (CSAF)
  4. Digi International security notice: Treck TCP/IP stack Ripple20
  5. CERT@VDE VDE-2021-028: Pepperl+Fuchs VDM100 EIP/G2
  6. CISA KEV
  7. FIRST EPSS

Frequently asked questions

How is CVE-2020-11901 exploited?

Through a DNS answer. The CVE text says a single invalid DNS response allows remote code execution, and CISA places the bug in the Treck DNS resolver, so the attacker has to answer a DNS query the device sends; NVD rates the attack complexity high for that reason (per NVD and CISA ICSA-20-168-01).

Is every Treck-based device affected by CVE-2020-11901?

No. Only builds that use the Treck DNS resolver are. CERT/CC records Aruba Networks as affected by CVE-2020-11896 but not by CVE-2020-11901, while Digi and Pepperl+Fuchs list this CVE for their products (per CERT/CC VU#257161, Digi and VDE-2021-028).

Which version fixes CVE-2020-11901?

CERT/CC and CISA say to update to Treck TCP/IP 6.0.1.67 or later; NVD lists versions before 6.0.1.66 as affected. For a finished device the fix is the vendor's firmware, such as Digi's releases from the week of 2020-04-20 (per CERT/CC, CISA, NVD and Digi).

Is CVE-2020-11901 in the CISA KEV catalog?

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.2161, the 97.7th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).