Mitsubishi Electric MELSEC controllers run production lines across automotive, electronics, semiconductor, packaging and water treatment plants, particularly in Asia. Despite that footprint, the platform gets far less defender attention than Siemens or Rockwell. This guide covers the network attack surface of the MELSEC iQ-R series, the advisories CISA has published against it, and the controls that reduce risk in a live plant.

Why the iQ-R network surface matters

An iQ-R system is a modular rack: a CPU module, optionally Ethernet modules such as the RJ71EN71, and I/O. Two services matter most for security.

  • SLMP (Seamless Message Protocol): a TCP/UDP request-response protocol that lets HMIs, MES gateways and third-party software read and write device memory. Like Modbus/TCP, it has no meaningful authentication on a default configuration. Anyone who can reach the configured SLMP port can read process values and, if write access is permitted, change them.
  • MELSOFT connectivity: the engineering protocol used by GX Works to upload, download and monitor programs. Exposure of the MELSOFT transmission port gives an attacker a path to program logic.

Both services typically live on user-configured ports, so scanning for a fixed default is unreliable. Asset inventory must record which ports each module actually exposes.

Verified advisories

CISA has published repeated advisories on the iQ-R family. Examples confirmed against CISA’s pages:

  • ICSA-22-335-01 (CVE-2022-40265, CVSS 8.6): a remote, unauthenticated attacker can cause denial of service on affected Ethernet/CPU network components using crafted packets. Recovery requires a system reset. Fixed firmware is listed for the RJ71EN71 and R-series CPU network functions.
  • ICSA-22-165-03 (CVE-2022-25163, CVSS 8.1): an input validation flaw in web functions that can lead to remote code execution or denial of service on affected MELSEC modules.
  • ICSA-21-147-05 (CVE-2021-20591, CVSS 5.3): reported by Nozomi Networks. Mitigations include IP filtering and the MELSOFT transmission port settings.
  • ICSA-20-324-05: a resource-consumption flaw (CVSS 7.5) that can cause denial of service across several iQ-R CPU firmware versions.

Check the current CISA and Mitsubishi Electric advisory pages for exact affected firmware versions before acting. Version lists change across updates and are not reproduced here.

Physical and operational impact

The pattern across these advisories is denial of service against the controller or its network module. In a plant, a stopped CPU or unresponsive Ethernet module is not a harmless outage:

  • A line controller that halts leaves conveyors, presses or robots stopped mid-cycle, which can scrap in-process product and require manual restart sequences.
  • In batch processes, an unexpected controller reset can leave valves and heaters in their fail states while the batch recipe is lost.
  • Because recovery for CVE-2022-40265 requires a system reset, an attacker or a misbehaving scanner can force repeated downtime until the module is isolated.
  • Remote code execution flaws in web functions add the risk of altered logic or setpoints, which carries safety and quality consequences beyond downtime.

Hardening

  1. Never expose SLMP or MELSOFT to the internet or the corporate IT network. Place controllers in a dedicated cell zone and allow access only from named engineering workstations, HMIs and gateways, in line with IEC 62443 zone-and-conduit design.
  2. Use the PLC’s built-in IP filter to restrict which hosts may connect, and disable unused Ethernet services including web server functions where not required.
  3. Disable unused MELSOFT and SLMP ports and set the minimum required access: read-only SLMP for monitoring systems, with writes restricted to specific hosts.
  4. Apply firmware updates from Mitsubishi Electric during planned maintenance windows, prioritizing modules in advisories with unauthenticated network impact.
  5. Put engineering access behind a jump host with MFA, and keep GX Works machines off general-purpose networks.
  6. Protect program integrity: keep offline, hashed copies of known-good project files so unexpected changes can be compared and restored.

Detection

  • Baseline SLMP and MELSOFT talkers. Passive monitoring (Zeek, Nozomi, Claroty, Dragos or a SPAN-fed sensor) should alert on any new source IP communicating with a controller on these ports.
  • Alert on write and program-transfer activity outside change windows. Writes from an HMI that previously only read are a strong signal.
  • Watch for malformed or high-rate traffic to Ethernet modules, which is the trigger pattern for the denial-of-service advisories.
  • Monitor controller health: CPU error LEDs, module watchdog events and unexpected restarts should feed the OT SIEM, not just the maintenance log.
  • Check for exposure: run authorized internal scans at low rates (aggressive scanning can itself crash older modules) and review external attack surface for exposed MELSEC services.

Takeaway

The iQ-R series is a mature, widely deployed platform whose main risks are unauthenticated network protocols and repeated denial-of-service flaws. Segmentation, IP filtering, disciplined firmware management and passive monitoring address most of them without touching running logic.

Sources: CISA ICSA-22-335-01, ICSA-22-165-03, ICSA-21-147-05, ICSA-20-324-05.

Tags
Mitsubishi ElectricMELSEC iQ-RPLCSLMPMELSOFTdenial-of-serviceCVE-2022-40265CVE-2022-25163CVE-2021-20591hardening