Vulnerability in Platform Mechanism AutoIP
SICK received a report from IOActive that informed SICK about a security vulnerability within the platform mechanism AutoIP, used by multiple devices. SICK recommends updating to the newest version. Refer to the recommended remediations for affected products where no update is available. Currently SICK is not aware of any public exploits specifically targeting this vulnerability.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-2075US | high7.5 | — | ||
Platform mechanism AutoIP allows remote attackers to reboot the device via a crafted packet in SICK AG solutions Bulkscan LMS111, Bulkscan LMS511, CLV62x – CLV65x, ICR890-3, LMS10x… | ||||
references
External citations — patches, advisories, analysis.
remediations (17)
- FixedSICK Bulkscan LMS111 with Firmware <1.04
Update to version V1.04 SICK removed the AutoIP weakness with the same available fix for the MSC800. The update can only be implemented by a SICK service technician, either by remote access or on site. To obtain the update, please contact your local service technician.
- FixedSICK Bulkscan LMS511 with Firmware <2.3
Update to version V2.30 SICK removed the AutoIP weakness with the same available fix for the MSC800. The update can only be implemented by a SICK service technician, either by remote access or on site. To obtain the update, please contact your local service technician.
- FixedSICK LMS10x with Firmware <2.0
Update to version V2.0 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK LMS11x with Firmware <2.0
Update to version V2.0 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK LMS12x with Firmware <2.1
Update to version V2.10 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK LMS13x with Firmware <2.1
Update to version V2.10 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK LMS14x with Firmware <2.1
Update to version V2.10 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK LMS15x with Firmware <2.0
Update to version V2.0 The update fixes, that the LMS1xx series does not reboot anymore, after it received an incorrect payload on the AutoIP port. There are no known limitations. The update to version V2.0 respectively V2.10 will be available from mid-October 2020 on. To get the latest LMS1xx firmware update, please contact the responsible SICK Sales and Service unit, or download it from sick.com.
- FixedSICK MSC800 with Firmware <4.1
Update to version V4.1 The update fixes that the MSC800 does not reboot anymore after it received an incorrect payload on the AutoIP port. There are no known limitations. To get the latest MSC800 firmware update please contact the responsible SICK Sales and Service unit. They can support if there is the need to consider any customer specific changes or constraints related to legal for trade systems.
- WorkaroundSICK CLV62x with Firmware <=6.10
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK CLV63x with Firmware <=6.10
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK CLV64x with Firmware <=6.10
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK CLV65x with Firmware <=6.10
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK ICR890-3 all Firmware versions
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK LMS53x all Firmware versions
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK LMS5xx all Firmware versions
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
- WorkaroundSICK RFH all Firmware versions
Restrict or block access to UDP port 30718 for the affected products. This workaround reduces the risk of the exploitation of the vulnerability but also limits the AutoIP function.
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