dbcve.org
Mc Works32Application · Mitsubishielectric

CVE-2020-12013

CRITICAL · 9.1 CVSS v3.1 Published 2020-07-16
Fix available
A fix is available. Upgrade to after 10.95.208.31 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A specially crafted WCF client that interfaces to the may allow the execution of certain arbitrary SQL commands remotely. This affects: Mitsubishi Electric MC Works64 Version 4.02C (10.95.208.31) and earlier, all versions; Mitsubishi Electric MC Works32 Version 3.00A (9.50.255.02); ICONICS GenBroker64, Platform Services, Workbench, FrameWorX Server v10.96 and prior; ICONICS GenBroker32 v9.5 and prior.

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

This is a SQL injection vulnerability in the WCF (Windows Communication Foundation) client interface of multiple industrial control software products. A specially crafted WCF client can inject and execute arbitrary SQL commands on the backend database, potentially allowing complete database compromise including data exfiltration or manipulation.

MitigationImplement proper input validation and parameterized queries/prepared statements in the WCF client interface to prevent SQL injection. Apply vendor-provided patches for affected Mitsubishi Electric MC Works and ICONICS products, or upgrade to patched versions.

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
Mc Works32Application
Affected:= 9.50.255.02
Mc Works64Application
Affected:<= 10.95.208.31
Energy AnalytixApplication
Affected:all versions
Facility AnalytixApplication
Affected:all versions
Genesis64Application
Affected:all versions
Hyper HistorianApplication
Affected:all versions
MobilehmiApplication
Affected:all versions
Quality AnalytixApplication
Affected:all versions

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
High
Integrity
High
Availability
None

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

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. Identify installed Mitsubishi Electric MC Works version
    Check the installed version of Mc Works32 or Mc Works64 via Windows Programs and Features (Add/Remove Programs), or locate the application executable and check its version properties. Common paths include C:\Program Files\Mitsubishi Electric\MC Works32\ or C:\Program Files (x86)\Mitsubishi Electric\MC Works64\
    Affected if Mc Works32 version equals 9.50.255.02, or Mc Works64 version is less than or equal to 10.95.208.31
  2. Identify installed ICONICS product and version
    Check Windows Programs and Features for any installed ICONICS products: Energy Analytix, Facility Analytix, Genesis64, Hyper Historian, MobileHMI, or Quality Analytix. Check the installation directory for version information, typically in C:\Program Files\ICONICS\ or C:\Program Files (x86)\ICONICS\
    Affected if Any of the listed ICONICS products are installed, as all versions are affected
  3. Verify WCF client interface configuration
    Examine the configuration files in the application installation directory for WCF client definitions. Look for .config files (such as app.config or *.exe.config) containing <system.serviceModel> sections with <client> endpoints. These define WCF client connections used by the application.
    Affected if WCF client endpoints are configured and the application connects to backend databases via these WCF interfaces
  4. Check for database connectivity from affected applications
    Review application logs, database connection strings, or network monitoring to determine if the application queries a backend database. SQL injection via WCF client requires the application to have active database connectivity.
    Affected if The affected application is configured to connect to a SQL database that could receive injected queries

You are affected if any Mitsubishi Electric MC Works32 (version 9.50.255.02), MC Works64 (version <= 10.95.208.31), or any ICONICS product (Energy Analytix, Facility Analytix, Genesis64, Hyper Historian, MobileHMI, Quality Analytix) is installed and configured with an active WCF client interface connecting to a backend database.

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 10.95.208.31
Interim mitigation

Implement proper input validation and parameterized queries/prepared statements in the WCF client interface to prevent SQL injection. Apply vendor-provided patches for affected Mitsubishi Electric MC Works and ICONICS products, or upgrade to patched versions.

Fix this in Mc Works32 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12013 — 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-12013 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