dbcve.org
Mc WorksApplication · Mitsubishielectric

CVE-2020-12011

CRITICAL · 9.8 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 communication packet sent to the affected systems could cause a denial-of-service condition or allow remote code execution. This issue affects: Mitsubishi Electric MC Works64 version 4.02C (10.95.208.31) and earlier, all versions; MC Works32 version 3.00A (9.50.255.02); ICONICS GenBroker64, Platform Services, Workbench, FrameWorX Server version 10.96 and prior; GenBroker32 version 9.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 · high confidence

A specially crafted communication packet sent to affected Mitsubishi Electric MC Works (32/64-bit) and ICONICS GenBroker/Platform Services/Workbench/FrameWorX Server software can cause denial of service or enable remote code execution due to improper handling of network communications.

MitigationApply vendor patches or updates to the affected software versions immediately. Implement network segmentation and restrict external access to affected ICS/OT systems to limit attack surface.

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 WorksApplication
Affected:<= 10.95.208.31
Mc Works32Application
Affected:= 9.50.255.02
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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify installed Mitsubishi Electric MC Works version
    Check the installed version of MC Works or MC Works32 via the Windows Add/Remove Programs panel, or look in the installation directory for version information files. Common locations: C:\Program Files\Mitsubishi Electric\MC Works\ or check registry under HKLM\SOFTWARE\Mitsubishi Electric\MC Works
    Affected if Version is <= 10.95.208.31 (for MC Works) or exactly 9.50.255.02 (for MC Works32)
  2. Identify installed ICONICS software products
    Check Windows Add/Remove Programs for installed ICONICS products including GenBroker, Platform Services, Workbench, FrameWorX Server, Energy Analytix, Facility Analytix, Genesis64, Hyper Historian, MobileHMI, or Quality Analytix. Also check the installation directory (typically C:\Program Files\ICONICS\)
    Affected if Any ICONICS product from the affected list is installed (note: the CVE states all versions are affected)
  3. Verify if GenBroker service is running
    Open Windows Services console (services.msc) and look for 'ICONICS GenBroker' service, or use command: sc query GenBroker. Also check Task Manager for genbroker.exe process
    Affected if GenBroker service exists and is running - this is the primary affected component for ICONICS
  4. Check network exposure of affected services
    Use netstat -an to list listening ports. Look for ports associated with ICONICS services (commonly ports 80, 443, or custom ports). Check firewall rules and network segmentation to determine if these services are accessible from outside the local network
    Affected if The affected software network services are listening on exposed network interfaces accessible from untrusted networks
  5. Verify Platform Services or FrameWorX Server presence
    Check Windows Services for 'ICONICS Platform Services' or 'FrameWorX Server' services. These may run as Windows services and can be queried via: sc query type= service state= all | findstr -i "ICONICS" or "FrameWorX"
    Affected if These ICONICS services are installed and running

Your environment is affected if you have any version of the listed ICONICS products installed, or Mitsubishi MC Works version <= 10.95.208.31 or exactly 9.50.255.02, and these services are network-accessible.

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

Apply vendor patches or updates to the affected software versions immediately. Implement network segmentation and restrict external access to affected ICS/OT systems to limit attack surface.

Fix this in Mc Works Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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