Mitsubishi Electric CNC Series (Update B)
Successful exploitation of this vulnerability could allow a local attacker to execute malicious code by getting setup-launcher to load a malicious DLL.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-2542US | high7.8 | — | ||
Untrusted search path vulnerability in Flexera InstallShield through 2015 SP1 allows local users to gain privileges via a Trojan horse DLL in the current working directory of a set… | ||||
references
External citations — patches, advisories, analysis.
- ICS Advisory ICSA-25-205-01 JSONself
- ICS Advisory ICSA-25-205-01 - Web Versionself
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
remediations (23)
- MitigationMS Configurator
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationMitsubishi Electric CNC communication software runtime library M70LC
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationMitsubishi Electric CNC communication software runtime library M730LC
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationMitsubishi Electric Numerical Control Device Communication Software (FCSB1224)
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Analyzer
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Analyzer2
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Configurator2
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Designer
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Designer2
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Explorer
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Monitor
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Monitor2
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Trainer
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Trainer plus
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Trainer2
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Trainer2 plus
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Virtual Simulator
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationNC Visualizer
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- MitigationRemote Monitor Tool
Before running the setup-launcher, make sure that no DLL exists in the folder containing the setup-launcher executable file (the name varies depending on the product) for the product.
- FixedMitsubishi Electric Numerical Control Device Communication Software (FCSB1224)
Please download and install the fixed version from the Mitsubishi Electric download site: Mitsubishi Electric Numerical Control Device Communication Software (FCSB1224): "A9" or later https://www.mitsubishielectric.com/fa/download/index.html.
- FixedNC Trainer2
Please download and install the fixed version from the Mitsubishi Electric download site: NC Trainer2: "AC" or later https://www.mitsubishielectric.com/fa/download/index.html.
- FixedNC Trainer2 plus
Please download and install the fixed version from the Mitsubishi Electric download site: NC Trainer2 plus: "AC" or later https://www.mitsubishielectric.com/fa/download/index.html.
- FixedNC Virtual Simulator
Please download and install the fixed version from the Mitsubishi Electric download site: NC Virtual Simulator: "A5" or later https://www.mitsubishielectric.com/fa/download/index.html.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan