CVE-2022-31800
highpriority · track · 41OT risk · elevatedEPSS 0.016 · 75 %ileDEEURUUSEPSS · scored 2026-10-27
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
No vendor fix yet; a mitigation is available.
- Mitigationphoenix_contact_psirt
Phoenix Contact classic line controllers are designed and developed for the use in closed industrial networks. The controller doesn't feature logic integrity and authenticity checks by design. Phoenix Contact therefore strongly recommends using the devices exclusively in closed networks and protected by a suitable firewall. Customers using Phoenix Contact classic line controllers are recommended to operate the devices in closed networks or protected with a suitable firewall as intended. Generic information and recommendations for security measures to protect network-capable devices can be found in the application note.
- MitigationAXC 1050cisa_csaf_ot
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 XCcisa_csaf_ot
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationAXC 3050cisa_csaf_ot
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 ETHcisa_csaf_ot
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 1x0cisa_csaf_ot
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 1x1cisa_csaf_ot
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/GPRScisa_csaf_ot
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
- MitigationILC 3xxcisa_csaf_ot
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 BASICcisa_csaf_ot
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 SRTcisa_csaf_ot
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-IBcisa_csaf_ot
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-IBcisa_csaf_ot
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 3TXcisa_csaf_ot
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-Scisa_csaf_ot
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 3TXcisa_csaf_ot
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 3TXcisa_csaf_ot
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 4TXcisa_csaf_ot
Connections between the engineering tools and the controller must always be in a locally protected environment or protected by VPN for remote access.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 9–10
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (102)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- VDE-2022-025PHOENIX CONTACT: Vulnerability in classic line industrial controllers2022-06-21csaf · phoenix_contact_psirtDE
The affected devices insufficiently verify uploaded data.
- ICSA-22-172-03Phoenix Contact Classic Line Controllers2022-06-21icsa · cisa_csaf_otUS
Successful exploitation of this vulnerability could allow an attacker to upload logic with arbitrary code.
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://cert.vde.com/en/advisories/VDE-2022-025/cnnvd
- https://cxsecurity.com/cveshow/CVE-2022-31800/cnnvd
- https://dam-mdc.phoenixcontact.com/asset/156443151564/0a870ae433c19148b80bd760f3a1c1f2/107913_en_03.pdfPatchcnnvd
- https://us-cert.cisa.gov/ics/advisories/icsa-22-172-03cnnvd
- https://www.auscert.org.au/bulletins/ESB-2022.3043cnnvd
- https://cert.vde.com/en/advisories/VDE-2022-025/enisa_euvd
- https://cert.vde.com/en/advisories/VDE-2022-025/ExploitThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan