dbcve.org
Cpu Module Logging Configuration ToolPlugin / extension · Mitsubishielectric

CVE-2020-5603

HIGH · 7.5 CVSS v3.1 Published 2020-06-30
Fix available
A fix is available. Upgrade to after 1.590q or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Uncontrolled resource consumption vulnerability in multiple Mitsubishi Electric FA Engineering Software products (GX Works2, GX Works3, GT Designer3, and 17 others) allows attackers to cause denial of service via unspecified vectors. The vulnerability stems from improper resource management that can be exploited to exhaust system resources.

MitigationApply vendor-supplied patches to update to fixed versions of each affected product (e.g., CW Configurator Ver. 1.010M and later, GX Works2 Ver. 1.586M and later). If patches unavailable, implement network segmentation and monitor for anomalous resource consumption patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cpu Module Logging Configuration ToolPlugin / extension
Affected:<= 1.94y
Cw ConfiguratorApplication
Affected:<= 1.010l
Em ConfiguratorApplication
Affected:<= 1.010l
Gt Designer3Application
Affected:<= 1.221f
Gx LogviewerApplication
Affected:<= 1.100e
Gx Works2Application
Affected:<= 1.590q
Gx Works3Application
Affected:<= 1.060n
M Commdtm HartApplication
Affected:<= 1.01b

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. List installed Mitsubishi Electric engineering software
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion | Where-Object {$_.DisplayName -match 'Mitsubishi|GX|GT|CW|EM|Logviewer|Logging|M Commdtm'}
    Affected if Any of these products appear in the installed programs list: Cpu Module Logging Configuration Tool, CW Configurator, EM Configurator, GT Designer3, GX Logviewer, GX Works2, GX Works3, or M Commdtm HART
  2. Verify the exact version number of each installed product
    Right-click each application shortcut, select Properties, and check the version field under the Details tab. Alternatively, open the application and navigate to Help > About or the version information dialog
    Affected if The displayed version matches one of the affected ranges: Cpu Module Logging Configuration Tool <= 1.94y, CW Configurator <= 1.010l, EM Configurator <= 1.010l, GT Designer3 <= 1.221f, GX Logviewer <= 1.100e, GX Works2 <= 1.590q, GX Works3 <= 1.060n, or M Commdtm HART <= 1.01b
  3. Compare installed version against affected version thresholds
    Use a text comparison or version comparison tool. For version strings like 1.010l, note that versions are compared numerically: 1.010l means version 1.010 (letter l is part of the build identifier). Any version number at or below the threshold listed is affected
    Affected if Your installed version number is equal to or lower than the specified threshold for your product
  4. Confirm the software is in active use or reachable on the network
    Check if the software is installed on a system that is networked or regularly used for engineering tasks. Open Task Manager or use Get-Process to see if any Mitsubishi processes are running (such as GXWorks2, GXWorks3, or GT Designer3)
    Affected if The vulnerable version is installed and the software is in use or exposed on the network, making it a potential target for resource exhaustion attacks

You are affected if any of these eight Mitsubishi Electric engineering software products are installed with a version number at or below the specified threshold for that product.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.590q
Interim mitigation

Apply vendor-supplied patches to update to fixed versions of each affected product (e.g., CW Configurator Ver. 1.010M and later, GX Works2 Ver. 1.586M and later). If patches unavailable, implement network segmentation and monitor for anomalous resource consumption patterns.

Fix this in Cpu Module Logging Configuration Tool Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5603 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data