Mitsubishi Electoric FA Engineering Software (CPU Module Logging Configuration Tool Ver. 1.94Y and earlier, CW Configurator Ver. 1.010L and earlier, EM Software Development Kit (EM Configurator) Ver. 1.010L and earlier, GT Designer3 (GOT2000) Ver. 1.221F and earlier, GX LogViewer Ver. 1.96A and earlier, GX Works2 Ver. 1.586L and earlier, GX Works3 Ver. 1.058L and earlier, M_CommDTM-HART Ver. 1.00A, M_CommDTM-IO-Link Ver. 1.02C and earlier, MELFA-Works Ver. 4.3 and earlier, MELSEC-L Flexible High-Speed I/O Control Module Configuration Tool Ver.1.004E and earlier, MELSOFT FieldDeviceConfigurator Ver. 1.03D and earlier, MELSOFT iQ AppPortal Ver. 1.11M and earlier, MELSOFT Navigator Ver. 2.58L and earlier, MI Configurator Ver. 1.003D and earlier, Motion Control Setting Ver. 1.005F and earlier, MR Configurator2 Ver. 1.72A and earlier, MT Works2 Ver. 1.156N and earlier, RT ToolBox2 Ver. 3.72A and earlier, and RT ToolBox3 Ver. 1.50C and earlier) allows an attacker to conduct XML External Entity (XXE) attacks via unspecified vectors.
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cpu_module_logging_configuration_tool | Mitsubishielectric | * | 1.94y (including) |
| Cw_configurator | Mitsubishielectric | * | 1.010l (including) |
| Em_configurator | Mitsubishielectric | * | 1.010l (including) |
| Gt_designer3 | Mitsubishielectric | * | 1.221f (including) |
| Gx_logviewer | Mitsubishielectric | * | 1.100e (including) |
| Gx_works2 | Mitsubishielectric | * | 1.590q (including) |
| Gx_works3 | Mitsubishielectric | * | 1.060n (including) |
| M_commdtm-hart | Mitsubishielectric | * | 1.01b (including) |
| M_commdtm-io-link | Mitsubishielectric | * | 1.03d (including) |
| Melfa-works | Mitsubishielectric | * | 4.4 (including) |
| Melsec-l_flexible_high-speed_i/o_control_module_configuration_tool | Mitsubishielectric | * | 1.005f (including) |
| Melsoft_fielddeviceconfigurator | Mitsubishielectric | * | 1.04e (including) |
| Melsoft_iq_appportal | Mitsubishielectric | * | 1.14q (including) |
| Melsoft_navigator | Mitsubishielectric | * | 2.62q (including) |
| Mi_configurator | Mitsubishielectric | * | 1.004e (including) |
| Motion_control_setting | Mitsubishielectric | * | 1.006g (including) |
| Mr_configurator2 | Mitsubishielectric | * | 1.100e (including) |
| Mt_works2 | Mitsubishielectric | * | 1.160s (including) |
| Rt_toolbox2 | Mitsubishielectric | * | 3.73b (including) |
| Rt_toolbox3 | Mitsubishielectric | * | 1.60n (including) |
XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing. By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as “file:///c:/winnt/win.ini” designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents.