LiveActive security incident?Get immediate response
CVE Record

CVE-2020-16209: Fieldcomm Group HART-IP and hipserver - Stack-based Buffer Overflow

A malicious 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw affects Fieldcomm Group HART-IP components used around industrial communications. A remote attacker could send oversized messages that crash the device or potentially take control. The CVSS score is 9.8, so exposed deployments should be treated as urgent even though the provided sources do not show active exploitation.

Executive priority

Treat this as a high-priority OT exposure issue. The business concern is loss of control or availability in systems using affected HART-IP components, not just a software crash. Focus first on confirming whether the products exist and are reachable.

Technical view

CVE-2020-16209 is a stack-based buffer overflow, CWE-121, in Fieldcomm Group HART-IP release 1.0.0.0 and hipserver 3.6.1. The described trigger is a sufficiently large message payload to the interface, with possible impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to organizations using the affected HART-IP Developer Kit 1.0.0.0 or hipserver 3.6.1, especially where the interface is reachable over a network. Asset certainty may be low in OT environments without protocol-aware inventory.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle. The sources describe remote, unauthenticated exploitation potential with low attack complexity, but do not provide evidence of active exploitation or public weaponization.

Researcher notes

The supplied evidence supports affected products, versions, CWE, CVSS, and high-impact outcomes. It does not name a specific patch level, safe version, detection signature, or active exploitation. Avoid assuming broader HART-IP ecosystem impact beyond the listed Fieldcomm components.

Mitigation direction

  • Identify any HART-IP Developer Kit 1.0.0.0 or hipserver 3.6.1 deployments.
  • Check Fieldcomm Group and CISA advisory guidance for supported updates or replacements.
  • Remove direct untrusted network access to affected HART-IP interfaces.
  • Apply compensating access controls around affected OT communication paths.
  • Prioritize remediation for internet-routable or cross-zone reachable systems.

Validation and detection

  • Inventory hosts and software versions for Fieldcomm HART-IP and hipserver components.
  • Confirm whether affected interfaces are reachable from enterprise, remote access, or internet paths.
  • Review CISA ICSA-20-287-04 and vendor records for current remediation status.
  • Monitor affected systems for crashes or unexpected service restarts.
  • Document any compensating controls where upgrades are unavailable.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-16209 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-16209Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Fieldcomm GroupHART-IP Developer KitAll 1.0.0.0Listed
Fieldcomm GrouphipserverAll 3.6.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.