First published: Mon Oct 08 2018(Updated: )
The Auto-Maskin products utilize an undocumented custom protocol to set up Modbus communications with other devices without validating those devices. The originating device sends a message in plaintext, 48:65:6c:6c:6f:20:57:6f:72:6c:64, "Hello World" over UDP ports 44444-44446 to the broadcast address for the LAN. Without verification devices respond to any of these broadcast messages on the LAN with a plaintext reply over UDP containing the device model and firmware version. Following this exchange the devices allow Modbus transmissions between the two devices on the standard Modbus port 502 TCP. Impact: An attacker can exploit this vulnerability to send arbitrary messages to any DCU or RP device through spoofing or replay attacks as long as they have access to the network. Affected releases are Auto-Maskin DCU-210E RP-210E: Versions prior to 3.7 on ARMv7.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
Auto-maskin Rp 210e Firmware | ||
Arm Arm7 | <3.7 | |
Auto-maskin Rp 210e | ||
Auto-maskin Dcu 210e Firmware | ||
Auto-Maskin DCU 210E |
The devices should implement Modbus TCP Security Protocol (v21, 2018) per Modbus specifications over port 802 TCP, for Modbus TCP with encryption and authentication.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.