How Protocol Gateways May Introduce More Problems than They Solve
summary
Trend Micro researchers analyze 5 commercial protocol gateways (three real‑time, two data‑station) using a modified boofuzz fuzzer and find pervasive issues: resource exhaustion (two devices crash after ~400 malformed packets, one reboots under load), three gateways mishandle Modbus translation allowing valid packets to turn into writes, one exposes a root shell via ping test (Telnet without auth), and MQTT/cloud links lack auth or use repeatable crypto seeds. Tests show attacks can bypass ICS firewalls; fix path: inventory gateways, whitelist access, schedule firmware updates and deeper protocol inspection.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:31Protocol Gateway - Translator
- 3:40Where Is Protocol Gateway
- 5:30Two Types of Protocol Gateway
- 7:05We Were Looking for Vulnerabilities in ...
- 9:25Devices and Problems
- 12:14Resource Exhaustion / Dos
- 17:26Error in Protocol Translation (Realtime)
- 20:04Protocol Translation (Data Station)
- 26:39Apply What You Have Learned Today (1)
- 28:24Disclosed vulnerabilities Gateway
related talks
27mWIFI-Important Remote Attack Surface: Threat is Expanding
42mCloudy With a Chance of Exploits: Compromising Critical Infrastructure Through IIoT Cloud Solutions
32mThere and Back Again: Discovering OT Devices Across Protocol Gateways
43mIoT Security Challenges and Solutions
35mRoute to Bugs: Analyzing the Security of BGP Message Parsing
45mWhen Machines Can't Talk
37mFinding Vulnerabilities in IoT Embedded Devices Using Linux OS and Open Source Tools
44mCritical Zero Days Remotely Compromise the Most Popular Real-Time OS