CVE-2020-25928 is an INFRA:HALT flaw in the DNS client of HCC Embedded's NicheStack TCP/IP stack: a DNS response with a bad answer length field makes the parser read and write out of bounds, which can lead to remote code execution on the device. NVD scores it 9.8, and CISA says NicheStack and NicheLite are fixed in v4.3.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
3.6%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-25928 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| HCC Embedded InterNiche TCP/IP stack (NicheStack) | cpe:2.3:a:hcc-embedded:nichestack_tcp\/ip:4.0.1:*:*:*:*:*:*:* | before v4.3 (CISA ICSA-21-217-01); NVD's CPE lists 4.0.1 |
| HCC Embedded NicheLite | — | before v4.3 (CISA ICSA-21-217-01) |
What does this mean for affected devices?
CISA's INFRA:HALT advisory ICSA-21-217-01, first released 2021-08-05 and last updated 2021-12-16 (Update B), covers 14 vulnerabilities in HCC Embedded's InterNiche TCP/IP stack (NicheStack) and NicheLite, both listed as affected below v4.3. For this CVE it says "the routine for parsing DNS response packets does not check the response data length field of individual DNS answers, which may cause an out-of-bounds read/write", and the fix it gives is "HCC recommends users apply release v4.3 or later". The CVE record names the functions involved, dns_upcall(), getoffset() and dnc_set_answer(), and says the impact can be an information leak, a denial of service or remote code execution "depending on the context".
NVD scores it 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, and records CWE-125 (out-of-bounds read) and CWE-787 (out-of-bounds write); CISA's advisory gives the same 9.8 and classes it as CWE-130. NVD's CPE configuration lists only NicheStack 4.0.1, a narrower match than the "below v4.3" range in the CISA advisory (NVD).
CERT/CC's VU#608209 explains why device owners rarely know they run this code: NicheStack has shipped since the late 1990s into "a complex supply chain into major industries including devices in critical infrastructure", and missing SBOMs complicated the "identification of impacted devices". Forescout's INFRA:HALT research, published 2021-08-04 with JFrog, rates this DNS bug as the set's remote code execution case (vendor ID HCCSEC-000010), says HCC's patches are "available upon request", and counted more than 6,400 internet-facing devices showing NicheStack banners in a Shodan query of 2021-03-08. The device-vendor advisories that CERT/CC and CISA link, Siemens SSA-789208, Phoenix Contact VDE-2021-032 and Mitsubishi Electric 2021-022, list other INFRA:HALT CVEs and do not name this one, so no specific device model is tied to it in those sources.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0363, the 89.7th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
Device makers should find out whether their SDK or RTOS port carries NicheStack under its own name, then move to v4.3 or later or request HCC's patch. Forescout's mitigation for the DNS bugs is to disable the DNSv4 client if it is unused, or block DNSv4 traffic to the device. Our embedded TCP/IP stack vulnerabilities guide lists the INFRA:HALT fix and how to identify a rebranded stack, and our memory corruption fix guide covers the length checks such parsers need. The HTTP server overflow from the same disclosure is CVE-2021-31226, and the NAME:WRECK DNS parsing bugs in Nucleus NET include CVE-2020-27737.
Evidence
- DNS response parsing does not check the response data length of individual answers; OOB read/write; CWE-130; CVSS 9.8; InterNiche stack and NicheLite < 4.3 affected; HCC recommends v4.3 or later; initial release 2021-08-05, Update B 2021-12-16. — CISA ICSA-21-217-01 (CSAF)
- NVD CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), CWE-125 and CWE-787; CPE nichestack_tcp/ip 4.0.1; functions dns_upcall(), getoffset(), dnc_set_answer(). — NVD
- NicheStack in a complex supply chain including critical infrastructure devices; lack of SBOM complicated identification of impacted devices; vendor statements from Siemens (SSA-789208) and Phoenix Contact (VDE-2021-032). — CERT/CC VU#608209
- HCCSEC-000010, DNSv4, RCE, 9.8; all versions before 4.3 affected; patches available upon request; over 6,400 NicheStack instances on Shodan (query 2021-03-08); mitigation: disable DNSv4 client or block DNSv4 traffic. — Forescout Research Labs: INFRA:HALT
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.0363 (89.7th percentile), dataset 2026-11-16, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which NicheStack version fixes CVE-2020-25928?
CISA's ICSA-21-217-01 lists the InterNiche TCP/IP stack and NicheLite below v4.3 as affected and says "HCC recommends users apply release v4.3 or later". Forescout adds that HCC's patches are available on request, so device makers on an older copy can also ask HCC for the fix.
What can an attacker do with CVE-2020-25928?
Send a crafted DNS response to a device whose NicheStack DNS client is in use. Because the answer length field is not checked, the parser can read and write out of bounds; NVD and the CVE record list information leak, denial of service or remote code execution depending on the context, and NVD scores it 9.8.
Which devices are affected by CVE-2020-25928?
Any firmware that includes a NicheStack or NicheLite DNS client below v4.3. CERT/CC says NicheStack reached devices in critical infrastructure through a complex supply chain, but the Siemens, Phoenix Contact and Mitsubishi Electric INFRA:HALT advisories that CERT/CC and CISA link name other CVEs from the set, not this one.
Is there a workaround if the firmware cannot be updated?
Forescout recommends disabling the DNSv4 client if it is not needed, or blocking DNSv4 traffic to the device, and notes that internal DNS servers alone may not be enough because other INFRA:HALT bugs allow DNS spoofing. CERT/CC also suggests isolating affected devices and blocking anomalous packets.
Questions about this page?