WAGO: Controller with CODESYS 2.3 Runtime Denial-of-Service
An authenticated attacker can send a malformed packet to trigger a device crash via the CODESYS V2 runtime commands parsing. Update: 08.07.2024 release date of the updates has been changed.
describes (2)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-1620US | medium4.9 | — | ||
Multiple WAGO devices in multiple versions may allow an authenticated remote attacker with high privileges to DoS the device by sending a specifically crafted packet to the CODESYS… | ||||
| CVE-2023-1619US | — | — | ||
Multiple WAGO devices in multiple versions may allow an authenticated remote attacker with high privileges to DoS the device by sending a malformed packet. | ||||
references
External citations — patches, advisories, analysis.
remediations (4)
- Mitigation
If the PLC runtime is running, but you do not need it, you can deactivate the plc runtime programming port over the product settings in the web-based management. You can find this option under "Configuration > PLC Runtime Services > CODESYS 2 > communication enabled". As general security measures strongly WAGO recommends: 1. Use general security best practices to protect systems from local and network attacks. 2. Do not allow direct access to the device from untrusted networks. 3. Update to the latest firmware according to the table in chapter solutions. 4. Industrial control systems (ICS) should not be directly accessible from the Internet, but should be protected by consistently applying the defense-in-depth strategy. The BSI provides general information on securing ICS in the ICS Compendium (https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/ICS/ICS-Security_compendium.pdf).
- Mitigation
If the PLC runtime is running, but you do not need it, you can deactivate the plc runtime programming port over the product settings in the web-based management. You can find this option under "Configuration > PLC Runtime Services > CODESYS 2 > communication enabled". As general security measures strongly WAGO recommends: 1. Use general security best practices to protect systems from local and network attacks. 2. Do not allow direct access to the device from untrusted networks. 3. Update to the latest firmware according to the table in chapter solutions. 4. Industrial control systems (ICS) should not be directly accessible from the Internet, but should be protected by consistently applying the defense-in-depth strategy. The BSI provides general information on securing ICS in the ICS Compendium (https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/ICS/ICS-Security_compendium.pdf).
- Fixed
We recommend all affected users to update to the firmware version listed below: ## PFC200 Family | Order No. | Firmware Version | |-------------------------|------------------| | 750-8202/xxx-xxx | FW 22 Patch 2 | | 750-8203/xxx-xxx | FW 22 Patch 2 | | 750-8204/xxx-xxx | FW 22 Patch 2 | | 750-8206/xxx-xxx | FW 22 Patch 2 | | 750-8207/xxx-xxx | FW 22 Patch 2 | | 750-8208/xxx-xxx | FW 22 Patch 2 | | 750-8210/xxx-xxx | FW 22 Patch 2 | | 750-8211/xxx-xxx | FW 22 Patch 2 | | 750-8212/xxx-xxx | FW 22 Patch 2 | | 750-8213/xxx-xxx | FW 22 Patch 2 | | 750-8214/xxx-xxx | FW 22 Patch 2 | | 750-8216/xxx-xxx | FW 22 Patch 2 | | 750-8217/xxx-xxx | FW 22 Patch 2 | ## Ethernet Controller 4th Generation Family | Order No. | Firmware Version | |-------------------------|------------------| | 750-823 | FW 11 | | 750-332 | FW 11 | | 750-832/xxx-xxx | FW 11 | | 750-862 | FW 11 | | 750-890/xxx-xxx | FW 11 | | 750-891 | FW 11 | | 750-893 | FW 11 | ## Ethernet Controller 3rd Generation Family | Order No. | Firmware Version | |-------------------------|----------------------------------------| | 750-331 | FW 17 (after BACnet certification) | | 750-829 | FW 17 (after BACnet certification) | | 750-831/xxx-xxx | FW 17 (after BACnet certification) | | 750-852 | FW 17 (already available) | | 750-880/xxx-xxx | FW 17 (after BACnet certification) | | 750-881 | FW 17 (after BACnet certification) | | 750-882 | FW 17 (after BACnet certification) | | 750-885/xxx-xxx | FW 17 (after BACnet certification) | | 750-889 | FW 17 (after BACnet certification) |
- Fixed
We recommend all affected users to update to the firmware version listed below: ## PFC200 Family | Order No. | Firmware Version | |-------------------------|------------------| | 750-8202/xxx-xxx | FW 22 Patch 2 | | 750-8203/xxx-xxx | FW 22 Patch 2 | | 750-8204/xxx-xxx | FW 22 Patch 2 | | 750-8206/xxx-xxx | FW 22 Patch 2 | | 750-8207/xxx-xxx | FW 22 Patch 2 | | 750-8208/xxx-xxx | FW 22 Patch 2 | | 750-8210/xxx-xxx | FW 22 Patch 2 | | 750-8211/xxx-xxx | FW 22 Patch 2 | | 750-8212/xxx-xxx | FW 22 Patch 2 | | 750-8213/xxx-xxx | FW 22 Patch 2 | | 750-8214/xxx-xxx | FW 22 Patch 2 | | 750-8216/xxx-xxx | FW 22 Patch 2 | | 750-8217/xxx-xxx | FW 22 Patch 2 | ## Ethernet Controller 4th Generation Family | Order No. | Firmware Version | |-------------------------|------------------| | 750-823 | FW 11 | | 750-332 | FW 11 | | 750-832/xxx-xxx | FW 11 | | 750-862 | FW 11 | | 750-890/xxx-xxx | FW 11 | | 750-891 | FW 11 | | 750-893 | FW 11 | ## Ethernet Controller 3rd Generation Family | Order No. | Firmware Version | |-------------------------|----------------------------------------| | 750-331 | FW 17 (after BACnet certification) | | 750-829 | FW 17 (after BACnet certification) | | 750-831/xxx-xxx | FW 17 (after BACnet certification) | | 750-852 | FW 17 (already available) | | 750-880/xxx-xxx | FW 17 (after BACnet certification) | | 750-881 | FW 17 (after BACnet certification) | | 750-882 | FW 17 (after BACnet certification) | | 750-885/xxx-xxx | FW 17 (after BACnet certification) | | 750-889 | FW 17 (after BACnet certification) |
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