# CVE-2020-5603: Denial of service in Mitsubishi Electoric FA Engineering Software > Attackers can cause denial of service in Mitsubishi Electric FA Engineering Software via uncontrolled resource consumption. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 30 Jun 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-v5gg-h569-48vg ## What is CVE-2020-5603? CVE-2020-5603 is a high-severity denial of service vulnerability in Mitsubishi Electoric FA Engineering Software, published on 30 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Uncontrolled resource consumption vulnerability in 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 cause a denial of service (DoS) condition attacks via unspecified vectors. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2020-5603? It affects 20 products. Products: Mitsubishielectric Cpu Module Logging Configuration Tool, Mitsubishielectric Cw Configurator, Mitsubishielectric Em Configurator, Mitsubishielectric Gt Designer3, Mitsubishielectric Gx Logviewer, Mitsubishielectric Gx Works2, Mitsubishielectric Gx Works3, Mitsubishielectric M Commdtm-Hart, Mitsubishielectric M Commdtm-Io-Link, Mitsubishielectric Melfa-Works, Mitsubishielectric Melsec-L Flexible High-Speed I\/O Control Module Configuration Tool, Mitsubishielectric Melsoft Fielddeviceconfigurator, Mitsubishielectric Melsoft Iq Appportal, Mitsubishielectric Melsoft Navigator, Mitsubishielectric Mi Configurator, Mitsubishielectric Motion Control Setting, Mitsubishielectric Mr Configurator2, Mitsubishielectric Mt Works2, Mitsubishielectric Rt Toolbox2, Mitsubishielectric Rt Toolbox3. ## How do I fix CVE-2020-5603? No fix has been published for CVE-2020-5603 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-5603 being exploited? There is no known exploitation of CVE-2020-5603 in the wild and no public exploit code. ## Other vulnerabilities in Mitsubishi Electoric FA Engineering Software - [CVE-2020-14496](https://insights.sbomify.com/CVE-2020-14496/): Mitsubishi Electric Multiple Factory Automation Engineering Software Products (Update A) - Permission Issues (high 8.3) - [CVE-2020-5602](https://insights.sbomify.com/CVE-2020-5602/): XML external entity in Mitsubishi Electoric FA Engineering Software (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-5603 and fix it if it is affected. What it is: CVE-2020-5603 is a high-severity denial of service vulnerability in Mitsubishi Electoric FA Engineering Software, published on 30 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-5603 in the wild and no public exploit code. Affected product: Mitsubishi Electoric FA Engineering Software. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-5603/ (Markdown: https://insights.sbomify.com/CVE-2020-5603/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5603 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5603 - OSV: https://osv.dev/vulnerability/CVE-2020-5603 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-5603/ Summaries are generated and may contain mistakes; the official description above is the record.