WAGO: Multiple Vulnerabilities in I/O-Check Service
An attacker needs an authorized login on the device in order to exploit the herein mentioned vulnerabilities. The reported vulnerabilities allow a local attacker with valid login credentials who is able to create files on the device to change the devices settings, e.g. default gateway address, time server etc. and potentially execute code.
describes (20)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-5186US | high7.0 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service "I/O-Check" functionality of WAGO PFC 200. An attacker can send a specially crafted… | ||||
| CVE-2019-5185US | high7.0 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service "I/O-Check" functionality of WAGO PFC 200. An attacker can send a specially crafted… | ||||
| CVE-2019-5184US | high7.8 | — | ||
An exploitable double free vulnerability exists in the iocheckd service "I/O-Check" functionality of WAGO PFC 200. A specially crafted XML cache file written to a specific location… | ||||
| CVE-2019-5181US | high7.8 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). A specially… | ||||
| CVE-2019-5180US | high7.8 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). An attacker… | ||||
| CVE-2019-5179US | high7.8 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). An attacker… | ||||
| CVE-2019-5178US | high7.8 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). An attacker… | ||||
| CVE-2019-5177US | medium5.5 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). The destina… | ||||
| CVE-2019-5176US | medium5.5 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). An attacker… | ||||
| CVE-2019-5171US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). An attacker can send specially… | ||||
| CVE-2019-5170US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). A specially crafted XML cache… | ||||
| CVE-2019-5169US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). A specially crafted XML cache… | ||||
| CVE-2019-5182US | medium5.5 | — | ||
An exploitable stack buffer overflow vulnerability vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 Firmware version 03.02.02(14). An attacker… | ||||
| CVE-2019-5175US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). A specially crafted XML cache… | ||||
| CVE-2019-5174US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 version 03.02.02(14). A specially crafted XML cache file writ… | ||||
| CVE-2019-5173US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). A specially crafted XML cache… | ||||
| CVE-2019-5172US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). An attacker can send a special… | ||||
| CVE-2019-5168US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 version 03.02.02(14). An attacker can send a specially crafte… | ||||
| CVE-2019-5167US | high7.8 | — | ||
An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 version 03.02.02(14). At 0x1e3f0 the extracted dns value from… | ||||
| CVE-2019-5166US | high7.8 | — | ||
An exploitable stack buffer overflow vulnerability exists in the iocheckd service ‘I/O-Check’ functionality of WAGO PFC 200 version 03.02.02(14). A specially crafted XML cache file… | ||||
references
External citations — patches, advisories, analysis.
remediations (40)
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Mitigation
* Disable I/O-Check service. * Restrict network access to the device. * Do not directly connect the device to the internet. * Disable unused TCP/UDP-ports.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
- Fixed
The I/O-Check service protocol is only needed during installation and commissioning, not during normal operations. It is highly recommended to disable the I/O-Check service after commissioning. This is the easiest and securest way to protect your device from the listed vulnerabilities. Regardless of the action described above, the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020.
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