CVE-2023-6943
📋 TL;DR
This vulnerability allows remote unauthenticated attackers to execute arbitrary code on affected Mitsubishi Electric industrial control software by exploiting unsafe reflection in RPC communications. Attackers can specify paths to malicious libraries that get loaded and executed. Affected systems include EZSocket, GT Designer3, GX Works2/3, MELSOFT Navigator, MT Works2, MX Component, and MX OPC Server DA/UA.
💻 Affected Systems
- EZSocket
- GT Designer3 Version1(GOT1000)
- GT Designer3 Version1(GOT2000)
- GX Works2
- GX Works3
- MELSOFT Navigator
- MT Works2
- MX Component
- MX OPC Server DA/UA
📦 What is this software?
Ezsocket by Mitsubishielectric
Fr Configurator2 by Mitsubishielectric
Got1000 by Mitsubishielectric
Got2000 by Mitsubishielectric
Gx Works2 by Mitsubishielectric
Gx Works3 by Mitsubishielectric
Mc Works64 by Mitsubishielectric
Melsoft Navigator by Mitsubishielectric
Mt Works2 by Mitsubishielectric
Mx Component by Mitsubishielectric
⚠️ Risk & Real-World Impact
Worst Case
Complete system compromise allowing attackers to execute arbitrary code with highest privileges, potentially leading to industrial process disruption, data theft, or ransomware deployment across critical infrastructure.
Likely Case
Remote code execution leading to industrial control system compromise, data exfiltration, or lateral movement within OT networks.
If Mitigated
Limited impact if systems are air-gapped, have strict network segmentation, and proper access controls preventing unauthorized RPC connections.
🎯 Exploit Status
The vulnerability requires no authentication and involves simple RPC manipulation, making exploitation straightforward for attackers with network access.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Varies by product - refer to Mitsubishi Electric advisory for specific fixed versions
Vendor Advisory: https://www.mitsubishielectric.com/en/psirt/vulnerability/pdf/2023-020_en.pdf
Restart Required: Yes
Instructions:
1. Download appropriate patches from Mitsubishi Electric support portal. 2. Apply patches according to vendor instructions. 3. Restart affected systems. 4. Verify patch installation and functionality.
🔧 Temporary Workarounds
Network Segmentation
allIsolate affected systems from untrusted networks using firewalls and VLANs
Disable Unnecessary RPC Services
windowsDisable RPC services if not required for operations
🧯 If You Can't Patch
- Implement strict network access controls allowing only trusted IP addresses to connect to RPC services
- Deploy intrusion detection systems monitoring for RPC exploitation patterns and unauthorized library loading
🔍 How to Verify
Check if Vulnerable:
Check installed software versions against affected version ranges listed in the advisory
Check Version:
Check via Windows Programs and Features or software's About dialog
Verify Fix Applied:
Verify installed version is above the affected range and test RPC functionality remains operational
📡 Detection & Monitoring
Log Indicators:
- Unusual RPC connections from unauthorized sources
- Failed library loading attempts
- Process creation from unexpected paths
Network Indicators:
- RPC traffic to affected software ports from unauthorized sources
- Unusual library path specifications in RPC calls
SIEM Query:
source_ip NOT IN (trusted_ips) AND dest_port IN (135, 445, [software_specific_ports]) AND protocol=rpc
🔗 References
- https://jvn.jp/vu/JVNVU95103362
- https://www.cisa.gov/news-events/ics-advisories/icsa-24-030-02
- https://www.mitsubishielectric.com/en/psirt/vulnerability/pdf/2023-020_en.pdf
- https://jvn.jp/vu/JVNVU95103362
- https://www.cisa.gov/news-events/ics-advisories/icsa-24-030-02
- https://www.mitsubishielectric.com/en/psirt/vulnerability/pdf/2023-020_en.pdf