Emerson WirelessHART Gateway

published 2021-09-29 5y ago modified 2026-06-17 4mo ago also EUVD-2020-4346

cvss: 10.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

There is a flaw in the code used to configure the internal gateway firewall when the gateway's VLAN feature is enabled. If a user enables the VLAN setting, the internal gateway firewall becomes disabled resulting in exposure of all ports used by the gateway.

Is CVE-2020-12030 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-135-02 updated 2020-05-14 cvss 10.0

Emerson WirelessHART Gateway

Emerson Wireless 1410 Gateway >= 4.6.43, <= 4.7.84 Emerson Wireless 1420 Gateway >= 4.6.43, <= 4.7.84 Emerson Wireless 1552WU Gateway >= 4.6.43, <= 4.7.84
affected: mitigation “Emerson recommends end users update the firmware on VLAN-enabled Version 4 gateways as soon as possible.” emerson.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Emerson Wireless 1410 Gateway
Emerson Wireless 1420 Gateway
Emerson Wireless 1552WU Gateway

Classification

Weakness

CWE-284 Improper Access Control

References

us-cert.cisa.gov /ics/advisories/icsa-20-135-02
third-party-advisory, us-government-resource

Sources

CVE List CVE-2020-12030
NVD CVE-2020-12030

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.