Mitsubishi · Gt Designer3 Version1 · CVE-2023-6943
**Name of the Vulnerable Software and Affected Versions**
Mitsubishi Electric Corporation EZSocket versions 3.0 to 5.92
GT Designer3 Version1(GOT1000) versions 1.325P and prior
GT Designer3 Version1(GOT2000) versions 1.320J and prior
GX Works2 versions 1.11M and later
GX Works3 versions 1.106L and prior
MELSOFT Navigator versions 1.04E to 2.102G
MT Works2 versions 1.190Y and prior
MX Component versions 4.00A to 5.007H
MX OPC Server DA/UA all versions
FR Configurator2 all versions
**Description**
The issue is related to the use of externally-controlled input to select classes or code, also known as 'Unsafe Reflection'. This allows a remote unauthenticated attacker to execute malicious code by RPC with a path to a malicious library while connected to the products. The exploitation of this issue may enable a remote attacker to execute arbitrary code by injecting a reference to a malicious library into the loading process.
**Recommendations**
For EZSocket versions 3.0 to 5.92, update to a version outside of this range to mitigate the risk.
For GT Designer3 Version1(GOT1000) versions 1.325P and prior, update to a version later than 1.325P.
For GT Designer3 Version1(GOT2000) versions 1.320J and prior, update to a version later than 1.320J.
For GX Works2 versions 1.11M and later, no specific mitigation is provided for these versions as they are stated to be affected in a manner that suggests versions after 1.11M may not be vulnerable in the same way, but this is unclear.
For GX Works3 versions 1.106L and prior, update to a version later than 1.106L.
For MELSOFT Navigator versions 1.04E to 2.102G, update to a version outside of this range.
For MT Works2 versions 1.190Y and prior, update to a version later than 1.190Y.
For MX Component versions 4.00A to 5.007H, update to a version outside of this range.
For MX OPC Server DA/UA all versions, consider disabling the service until a patch is available.
For FR Configurator2 all versions, consider restricting access to the software until a patch is available.
As a temporary workaround, consider disabling any RPC functionality that allows for the execution of external code until a patch is available.