Security Advisory

CVE-2020-24338: AMNESIA:33 picoTCP DNS Decompression RCE

Last updated:
  • CVE-2020-24338

CVE-2020-24338 is an AMNESIA:33 flaw in the DNS name decompression code of the picoTCP embedded TCP/IP stack: a crafted DNS response with bad compression pointers makes pico_dns_decompress_name() write out of bounds, causing a crash or code execution. NVD scores it 9.8; original picoTCP is end of life, and picoTCP-NG merged a fix on 2026-09-11.

Vulnerability summary

CVSS base score

9.8

Critical severity

EPSS score (FIRST)

37.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

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

Affected components

ComponentCPEVersion range
picoTCP (DNS client, pico_dns_common.c)cpe:2.3:a:altran:picotcp:*:*:*:*:*:*:*:*1.7.0 and earlier (NVD); end of life per CISA ICSA-20-343-01
picoTCP-NG (virtualsquare/picotcp)—1.7.0 and earlier per CISA ICSA-20-343-01; fix merged to master on 2026-09-11 (PR #82), after the newest tag v2.1

What does this mean for affected devices?

CVE-2020-24338 is one of the 33 AMNESIA:33 vulnerabilities that Forescout researchers reported in open-source embedded TCP/IP stacks, disclosed on 2020-12-08. The CVE text says the DNS domain name record decompression in pico_dns_decompress_name() in pico_dns_common.c "does not validate the compression pointer offset values with respect to the actual data present in a DNS response packet, causing out-of-bounds writes that lead to Denial-of-Service and Remote Code Execution". NVD classes it as CWE-787 and scores it 9.8 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H for picoTCP through 1.7.0 (NVD). CERT/CC's VU#815128 applies it to both picoTCP and picoTCP-NG, and CISA's ICSA-20-343-01 (CSAF) gives the same 9.8 score, describing a domain-name parser that "lacks bounds checks, allowing an attacker to corrupt memory with crafted DNS packets"; it lists picoTCP 1.7.0 and earlier as end of life and picoTCP-NG 1.7.0 and earlier as affected.

Is there a fix for picoTCP?

The original picoTCP is end of life per CISA. The picoTCP-NG fork, picoTCP-NG, fixed it in commit 1922516, "Bound DNS name decompression to packet length (CVE-2020-24338/24339)". The commit message says the function "used a 0xC0 compression pointer as an unbounded offset (pico_dns_packet has no length field)", and the fix threads the packet length through the decompress helpers and bounds "every label walk and pointer target to the packet end", touching the DNS client, the shared DNS code and mDNS. It was merged on 2026-09-11 through pull request #82, which also fixes CVE-2020-24340 in mDNS and says a v2.2 release follows. On 2026-11-16 the repository's newest tag is still v2.1, so a firmware build from a tagged picoTCP-NG release lacks the fix.

Which devices does it reach?

picoTCP is a small TCP/IP stack linked into microcontroller firmware, and the bug sits in the DNS client, so a device is exposed when its image includes the DNS module and resolves names over a network an attacker can answer on. Devices that use static IP addresses with the DNS module compiled out do not include the vulnerable function. Neither the CERT/CC note nor the CISA advisory names a device product for this CVE, so the answer for a given product comes from the maker's own build records.

Is CVE-2020-24338 exploited?

It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.3723, the 98.5th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).

What should device makers do?

Find the picoTCP version and whether the DNS and mDNS modules are built, then backport commit 1922516 and the rest of PR #82 or move to a maintained stack, and rebuild. Until devices are updated, CERT/CC's AMNESIA:33 note advises keeping embedded devices off the internet and in segmented network zones. Our embedded TCP/IP stack vulnerabilities guide covers finding the stack in an image and recording a not-affected decision, and our memory corruption fix guide covers bounding parsers to the received length. The Contiki DNS64 flaw from the same disclosure is CVE-2020-24336, and a similar DNS name-parsing bug in another stack is CVE-2020-27736 in Nucleus NET.

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

  • picoTCP through 1.7.0: pico_dns_decompress_name() does not validate compression pointer offsets, out-of-bounds writes, DoS and RCE; NVD CVSS v3.1 9.8, CWE-787. — NVD
  • Affects PicoTCP and PicoTCP-NG DNS name decompression, DoS/RCE; advises keeping devices off the internet and in segmented zones. — CERT/CC VU#815128
  • CISA: CVSS 9.8; picoTCP (EOL) 1.7.0 and prior, picoTCP-NG 1.7.0 and prior. — CISA ICSA-20-343-01 (CSAF)
  • picoTCP-NG commit 1922516 bounds DNS name decompression to the packet length (CVE-2020-24338/24339). — picoTCP-NG commit 1922516
  • PR #82 merged 2026-09-11, also fixes CVE-2020-24340; says v2.2 is released afterwards; newest tag on 2026-11-16 is v2.1. — picoTCP-NG pull request #82
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.37226 (98.5th percentile), dataset 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT/CC VU#815128: Embedded TCP/IP stacks have memory corruption vulnerabilities
  3. CISA ICSA-20-343-01: Multiple Embedded TCP/IP Stacks (CSAF)
  4. picoTCP-NG commit 1922516: Bound DNS name decompression to packet length
  5. picoTCP-NG pull request #82: Fix two old CVE reports
  6. Forescout Vedere Labs: AMNESIA:33
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Is there a picoTCP release that fixes CVE-2020-24338?

Not a tagged one as of 2026-11-16. The original picoTCP is end of life per CISA; the picoTCP-NG fork merged the fix (commit 1922516, pull request #82) on 2026-09-11, and its newest tag is v2.1 (per CISA ICSA-20-343-01 and picoTCP-NG on GitHub).

What does an attacker need to exploit CVE-2020-24338?

The ability to send the device a DNS response, for example from a spoofed or malicious resolver on its network. NVD's vector is network, low complexity, no privileges and no user interaction (per NVD and CERT/CC VU#815128).

Does the picoTCP-NG fix cover other AMNESIA:33 CVEs?

Yes. Commit 1922516 is titled for CVE-2020-24338 and CVE-2020-24339, and pull request #82 also fixes CVE-2020-24340 in mDNS response handling (per picoTCP-NG on GitHub).

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

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