Critical vulnerabilities in SICK InspectorP61x, InspectorP62x and TiM3xx
Multiple critical vulnerabilities were found in the SICK products InspectorP61x, InspectorP62x and TiM3xx. If exploited, this potentially allows an attacker to impact availabiltiy, integrity and confidentaility of the products. It is strongly recommended to upgrade the InspectorP61x, InspectorP62x and TiM3xx to the latest release.
beschreibt (6)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2024-11022US | — | — | ||
The authentication process to the web server uses a challenge response procedure which
inludes the nonce and additional information. This challenge can be used several times for lo… | ||||
| CVE-2024-10776US | —OT erhöht | — | ||
Lua apps can be deployed, removed, started, reloaded or stopped without authorization via
AppManager. This allows an attacker to remove legitimate apps creating a DoS attack, read… | ||||
| CVE-2024-10774US | —OT erhöht | — | ||
Unauthenticated CROWN APIs allow access to critical functions. This leads to the accessibility of large parts of the web application without authentication. | ||||
| CVE-2024-10773US | — | — | ||
The product is vulnerable to pass-the-hash attacks in combination with hardcoded credentials of hidden user levels. This means that an attacker can log in with the hidden user leve… | ||||
| CVE-2024-10772US | — | — | ||
Since the firmware update is not validated, an attacker can install modified firmware on the
device. This has a high impact on the availabilty, integrity and confidentiality up to… | ||||
| CVE-2024-10771US | — | — | ||
Due to missing input validation during one step of the firmware update process, the product
is vulnerable to remote code execution. With network access and the user level ”Service”… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
Behebungen (14)
- MitigationSICK InspectorP61x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development for which the CROWN API is required should be done in a trusted environment. As soon as the device is used productively with the custom-developed apps, the CROWN API should be deactivated.
- MitigationSICK InspectorP61x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development should be done in a trusted environment. After the development, app management should be disabled.
- MitigationSICK InspectorP62x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development for which the CROWN API is required should be done in a trusted environment. As soon as the device is used productively with the custom-developed apps, the CROWN API should be deactivated.
- MitigationSICK InspectorP62x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development should be done in a trusted environment. After the development, app management should be disabled.
- BehobenSICK InspectorP61x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK InspectorP61x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK InspectorP61x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK InspectorP62x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK InspectorP62x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK InspectorP62x with Firmware < 5.0.0
Customers are strongly recommended to upgrade to the latest release.
- BehobenSICK TiM3xx with Firmware < 5.10.0
Customers are strongly recommended to upgrade to the latest release.
- WorkaroundInspectorP61x Firmware
As the communication is not encrypted, the device should only be used in a trusted environment.
- WorkaroundInspectorP62x Firmware
As the communication is not encrypted, the device should only be used in a trusted environment.
- WorkaroundSICK TiM3xx with Firmware < 5.10.0
We recommend updating the firmware only in a trusted environment.
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan