CVE-2020-12015
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 · uneditedA specially crafted communication packet sent to the affected systems could cause a denial-of-service condition due to improper deserialization. This issue 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 version 10.96 and prior; ICONICS 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 confidenceImproper deserialization vulnerability in MC Works and ICONICS GenBroker allows remote attackers to send specially crafted communication packets that cause a denial-of-service condition. The flaw exists in the deserialization handling of network communication in affected 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<= 10.95.208.31= 9.50.255.02all versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MC Works versionCheck the installed version of Mitsubishi Electric MC Works or MC Works32 through Windows Programs and Features, the application help menu, or the product's About dialog. Look for version information in the installation directory or registry under the product's uninstall entry.Affected if The installed version is MC Works <= 10.95.208.31 or MC Works32 = 9.50.255.02
-
Identify installed ICONICS productsEnumerate installed ICONICS software including Energy Analytix, Facility Analytix, Genesis64, Hyper Historian, MobileHMI, and Quality Analytix through Windows Programs and Features or by checking the ICONICS installation directory.Affected if Any of the listed ICONICS products are installed regardless of version (all versions affected)
-
Verify GenBroker service statusCheck if the GenBroker service is running on the system. On Windows, use Services.msc or run 'sc query GenBroker' from an elevated command prompt. Also check for the GenBroker.exe process in Task Manager.Affected if The GenBroker service is running and exposed to network communication, as the vulnerability exists in its deserialization handling of network packets
-
Check network exposure of affected servicesReview firewall rules and network configuration to determine if GenBroker or the affected SCADA/HMI services are listening on network ports and accessible from untrusted networks. Check for open ports typically used by these products.Affected if GenBroker or affected products are listening on network ports and accessible from untrusted or external networks, enabling remote attackers to send malicious packets
-
Compare installed versions against affected rangesDocument the exact version numbers of all installed Mitsubishi Electric and ICONICS products and compare them against the CVE-affected version ranges: MC Works <= 10.95.208.31, MC Works32 = 9.50.255.02, and all versions of ICONICS products.Affected if Any installed version falls within or matches the affected version ranges, indicating potential exposure to the deserialization vulnerability
The environment is affected if any MC Works version <= 10.95.208.31 or MC Works32 version 9.50.255.02 is installed, or if any ICONICS product (Energy Analytix, Facility Analytix, Genesis64, Hyper Historian, MobileHMI, or Quality Analytix) is installed, and the GenBroker service handling their network communication is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches for MC Works64 (version 4.02C+), MC Works32 (version 3.00A+), and ICONICS products (version 10.96+ for 64-bit, version 9.5+ for 32-bit). Consider network segmentation to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-12015 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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