CVE-2020-12011

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 29% (98th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 29%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
29%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 16, 2020

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Oct 4, 2026
Patch available. Sources: cisa.
cisa Patch Available

ICONICS GENESIS64, GENESIS32 | CISA

https://us-cert.cisa.gov/ics/advisories/icsa-20-170-03
cisa Patch Available

Mitsubishi Electric MC Works64, MC Works32 | CISA

https://us-cert.cisa.gov/ics/advisories/icsa-20-170-02

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:22 UTCEPSS rescore
  4. 2026-09-30 14:59 UTCEPSS rescore
  5. 2026-09-30 10:33 UTCEG score recompute
  6. 2026-09-27 13:40 UTCEPSS rescore
  7. 2026-09-26 15:54 UTCEPSS rescore
  8. 2026-09-24 13:59 UTCEPSS rescore
  9. 2026-09-22 14:43 UTCEPSS rescore
  10. 2026-09-21 20:28 UTCEPSS rescore
  11. 2026-09-19 15:37 UTCEPSS rescore
  12. 2026-09-18 19:23 UTCEPSS rescore
  13. 2026-09-17 19:22 UTCEPSS rescore
  14. 2026-09-16 14:04 UTCEPSS rescore
  15. 2026-09-16 14:04 UTCEPSS rescore
  16. 2026-09-15 03:06 UTCEPSS rescore
  17. 2026-09-12 14:56 UTCEPSS rescore
  18. 2026-09-11 14:48 UTCEPSS rescore
  19. 2026-09-11 09:32 UTCEPSS rescore
  20. 2026-09-06 13:44 UTCEPSS rescore
  21. 2026-09-05 15:24 UTCEPSS rescore
  22. 2026-09-04 13:56 UTCEPSS rescore
  23. 2026-09-02 14:08 UTCEPSS rescore
  24. 2026-08-30 19:14 UTCEPSS rescore
  25. 2026-08-30 01:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-28 21:37 UTCEPSS rescore
  2. 2026-08-27 14:21 UTCEPSS rescore
  3. 2026-08-26 14:42 UTCEPSS rescore
  4. 2026-08-25 13:45 UTCEPSS rescore
  5. 2026-08-20 22:51 UTCEPSS rescore
  6. 2026-08-19 17:00 UTCEPSS rescore
  7. 2026-08-18 13:44 UTCEPSS rescore
  8. 2026-08-16 14:52 UTCEPSS rescore
  9. 2026-08-16 02:11 UTCEPSS rescore
  10. 2026-08-15 01:26 UTCEPSS rescore
  11. 2026-08-13 21:57 UTCEPSS rescore
  12. 2026-08-12 13:47 UTCEPSS rescore
  13. 2026-08-08 16:33 UTCEPSS rescore
  14. 2026-08-07 16:23 UTCEPSS rescore
  15. 2026-08-06 13:43 UTCEPSS rescore
  16. 2026-08-05 19:14 UTCEPSS rescore
  17. 2026-08-04 15:06 UTCEPSS rescore
  18. 2026-08-04 10:34 UTCEPSS rescore
  19. 2026-08-01 04:12 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:27 UTCEPSS rescore
  22. 2026-07-28 15:32 UTCEPSS rescore
  23. 2026-07-26 14:51 UTCEPSS rescore
  24. 2026-07-25 14:14 UTCEPSS rescore
  25. 2026-07-24 14:14 UTCEPSS rescore
  26. 2026-07-23 14:15 UTCEPSS rescore
  27. 2026-07-23 14:15 UTCEPSS rescore
  28. 2026-07-23 01:48 UTCEG score recompute
  29. 2026-07-22 22:33 UTCEG score recompute
  30. 2026-07-22 14:05 UTCEPSS rescore
  31. 2026-07-21 15:22 UTCEPSS rescore
  32. 2026-07-21 15:22 UTCEPSS rescore
  33. 2026-07-20 17:04 UTCEPSS rescore
  34. 2026-07-19 02:26 UTCEPSS rescore
  35. 2026-07-19 02:26 UTCEPSS rescore
  36. 2026-07-18 10:02 UTCEPSS rescore
  37. 2026-07-16 16:59 UTCEPSS rescore
  38. 2026-07-16 16:59 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-13 22:27 UTCEPSS rescore
  41. 2026-07-13 06:10 UTCEPSS rescore
  42. 2026-07-13 06:10 UTCEPSS rescore
  43. 2026-07-12 05:44 UTCEPSS rescore
  44. 2026-07-11 08:24 UTCEPSS rescore
  45. 2026-07-09 19:06 UTCEPSS rescore
  46. 2026-07-08 15:11 UTCEPSS rescore
  47. 2026-07-07 13:43 UTCEPSS rescore
  48. 2026-07-06 16:25 UTCEPSS rescore
  49. 2026-07-06 16:25 UTCEPSS rescore
  50. 2026-07-05 02:27 UTCEPSS rescore
  51. 2026-07-01 15:03 UTCEPSS rescore
  52. 2026-07-01 15:03 UTCEPSS rescore
  53. 2026-06-29 14:04 UTCEPSS rescore
  54. 2026-06-29 14:04 UTCEPSS rescore
  55. 2026-06-28 04:54 UTCEPSS rescore
  56. 2026-06-28 04:54 UTCEPSS rescore
  57. 2026-06-27 03:06 UTCEPSS rescore
  58. 2026-06-25 13:47 UTCEPSS rescore
  59. 2026-06-25 13:47 UTCEPSS rescore
  60. 2026-06-24 14:03 UTCEPSS rescore
  61. 2026-06-24 14:03 UTCEPSS rescore
  62. 2026-06-23 21:31 UTCEPSS rescore
  63. 2026-06-23 21:31 UTCEPSS rescore
  64. 2026-06-22 14:23 UTCEPSS rescore
  65. 2026-06-22 14:23 UTCEPSS rescore
  66. 2026-06-21 14:54 UTCEPSS rescore
  67. 2026-06-21 14:54 UTCEPSS rescore
  68. 2026-06-21 01:57 UTCEPSS rescore
  69. 2026-06-21 01:57 UTCEPSS rescore
  70. 2026-06-19 19:23 UTCEPSS rescore
  71. 2026-06-19 19:23 UTCEPSS rescore
  72. 2026-06-18 17:50 UTCEPSS rescore
  73. 2026-06-18 17:50 UTCEPSS rescore
  74. 2026-06-17 17:50 UTCEPSS rescore
  75. 2026-06-17 17:50 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-12011?
CVE-2020-12011 is a critical vulnerability published on July 16, 2020. 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…
When was CVE-2020-12011 disclosed?
CVE-2020-12011 was first published on July 16, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-12011 actively exploited?
CVE-2020-12011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-12011?
CVE-2020-12011 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-12011?
A fix for CVE-2020-12011 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-12011

Explore →

Is Your Infrastructure Affected by CVE-2020-12011?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs