CVE-2020-16209 is a stack-based buffer overflow (CWE-121) in FieldComm Group's HART-IP reference code: hipserver 3.6.1 and the HART-IP Developer Kit 1.0.0.0 copy oversized HART-IP payloads into an internal buffer, which can crash the device or let an attacker take control. NVD scores it 9.8. It is fixed in hipserver 3.7.0, released 2020-10-05.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
1.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-16209 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| FieldComm Group hipserver (HART-IP reference server) | cpe:2.3:a:fieldcommgroup:hipserver:3.6.1:*:*:*:*:*:*:* | 3.6.1; fixed in 3.7.0 (2020-10-05) |
| FieldComm Group HART-IP Developer Kit firmware | cpe:2.3:o:fieldcommgroup:hart-ip_developer_kit_firmware:1.0.0.0:*:*:*:*:*:*:* | 1.0.0.0; hipserver 3.7.0 pairs with Developer Kit release 1.0.1.0 |
What does this mean for affected devices?
NVD's description of CVE-2020-16209 says an attacker "could exploit the interface of the Fieldcomm Group HART-IP (release 1.0.0.0) by constructing messages with sufficiently large payloads to overflow the internal buffer and crash the device, or obtain control of the device." NVD's Primary score is CVSS v3.1 9.8 (critical), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, the same as CISA's, and CISA records CWE-121, stack-based buffer overflow. NVD's CPE list names hipserver 3.6.1 and HART-IP Developer Kit firmware 1.0.0.0. CISA's SSVC entry in the record reads exploitation none, automatable yes, technical impact total (NVD).
Why does a reference implementation matter for devices?
Because device makers build on it. HART-IP carries HART commands over TCP and UDP and runs in I/O systems and WirelessHART gateways. FieldComm Group, which owns the HART protocol, publishes hipserver on GitHub as the server half of its HART-IP Developer Kit, and the 3.6.1 release notes call it the "initial public release" related to release 1.0.0.0 of the Developer Kit. A gateway, remote I/O or field device firmware whose HART-IP interface started from that code inherits the overflow regardless of whose brand is on the box, so product teams should check the provenance of their HART-IP code, not only vendor advisory lists.
CISA's ICSA-20-287-04, published 2020-10-13, credits Reid Wightman of Dragos with reporting the flaw, says a buffer overflow "may allow remote code execution", and lists commercial facilities and critical manufacturing among the affected sectors. Its remediation: "Users of hipserver should immediately upgrade source code to v3.7.0 or later" and restrict access to the computers or devices running the software (CISA CSAF of ICSA-20-287-04). NVD published its record on 2022-05-19, long after the fix.
What did the fix change?
The hipserver 3.7.0 release of 2020-10-05 says it includes "security upgrades made in response to a reported vulnerability described by CVE ID CVE-2020-16209, where an unchecked memory transfer in the IP interface could possibly overflow an internal buffer." Calls such as memcpy, memset, strcpy, strncpy and sprintf were replaced with bounds-checked versions from Intel's MIT-licensed safestringlib, and the release pairs with Developer Kit release 1.0.1.0. That is the standard remedy in our memory corruption fix guide; for another stack overflow in an OT protocol stack, see CVE-2022-4608 in the Hitachi Energy RTU500.
Our HART and WirelessHART security guide covers the HART-IP security model that FieldComm Group standardized in mid-2020, with TLS/DTLS and per-user credentials, and the gateway advisories that followed, such as CVE-2020-12030.
CVE-2020-16209 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.01548, the 75th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS). CISA reported no known public exploits specifically targeting it.
To fix it, rebuild from hipserver 3.7.0 or later, or port the bounds checks into any HART-IP code derived from 3.6.1, and keep HART-IP servers reachable only from the hosts that need them.
Evidence
- NVD description: Fieldcomm Group HART-IP (release 1.0.0.0), messages with sufficiently large payloads overflow the internal buffer and crash the device or obtain control. NVD Primary and CISA CVSS v3.1 9.8 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; CWE-121 (CISA); CPE hipserver 3.6.1 and hart-ip_developer_kit_firmware 1.0.0.0; CISA SSVC exploitation none, automatable yes, technical impact total; published 2022-05-19. — NVD
- CSAF ICSA-20-287-04 (2020-10-13): Fieldcomm Group hipserver 3.6.1 and HART-IP Developer kit 1.0.0.0; CWE-121; CVSS v3 9.8; buffer overflow may allow remote code execution; users of hipserver should immediately upgrade source code to v3.7.0 or later; restrict access; Reid Wightman, Dragos, reported; no known public exploits; sectors Commercial Facilities, Critical Manufacturing. — CISA ICSA-20-287-04 (CSAF)
- hipserver v3.7.0 released 2020-10-05: security upgrades for CVE-2020-16209, unchecked memory transfer in the IP interface; unsafe C library functions replaced with safestringlib (MIT); related to HART-IP Developer Kit release 1.0.1.0. v3.6.1 released 2019-12-05 as initial public release related to Developer Kit 1.0.0.0. — FieldComm Group hipserver releases (GitHub)
- Not in the CISA KEV catalog, version 2026.11.13, checked 2026-11-17. — CISA KEV
- EPSS 0.01548, percentile 0.7545, dataset 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which versions are affected by CVE-2020-16209?
FieldComm Group hipserver 3.6.1 and the HART-IP Developer Kit 1.0.0.0. CISA tells hipserver users to upgrade the source code to 3.7.0 or later (per NVD and CISA ICSA-20-287-04).
Does CVE-2020-16209 affect commercial HART-IP products?
CISA's advisory names only FieldComm Group's reference software. A product whose HART-IP interface was built from hipserver 3.6.1 code carries the same overflow, so check where your HART-IP code came from (per CISA ICSA-20-287-04 and the hipserver release notes).
How was CVE-2020-16209 fixed?
hipserver 3.7.0, released 2020-10-05, replaced unsafe C library calls such as memcpy, strcpy and sprintf with bounds-checked functions from Intel's safestringlib (per the hipserver 3.7.0 release notes).
Is CVE-2020-16209 in the CISA KEV catalog?
No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.01548, the 75th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?