Phoenix Contact Classic Line Controllers
Successful exploitation of this vulnerability could allow an attacker to upload logic with arbitrary code.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-31800US | high10.0OT elevated | — | ||
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device. | ||||
references
External citations — patches, advisories, analysis.
remediations (17)
- MitigationAXC 1050
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationAXC 1050 XC
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationAXC 3050
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationFC 350 PCI ETH
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 1x0
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 1x1
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 1x1 GSM/GPRS
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 3xx
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationPC WORX RT BASIC
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationPC WORX SRT
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 430 ETH-IB
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 450 ETH-IB
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 460R PN 3TX
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 460R PN 3TX-S
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 470 PN 3TX
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 470S PN 3TX
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationRFC 480S PN 4TX
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan