CVE-2019-10972 json
Mitsubishi Electric FR Configurator2, Version 1.16S and prior.
published 2019-07-25 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2686
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Mitsubishi Electric FR Configurator2, Version 1.16S and prior. This vulnerability can be triggered when an attacker provides the target with a rogue project file (.frc2). Once a user opens the rogue project, CPU exhaustion occurs, which causes the software to quit responding until the application is restarted.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-204-01 updated cvss 5.5
Mitsubishi Electric FR Configurator2
-
Mitsubishi Electric FR Configurator2 <= 1.16Saffected: mitigation “Mitsubishi Electric has released Version 1.17T for the reported vulnerabilities. Additional information about the vulnerabilities and how to obtain the update can be found at the following location:” mitsubishielectric.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.1 | AV:N/AC:M/Au:N/C:N/I:N/A:C |
Affected products
- Mitsubishi Electric Mitsubishi Electric FR Configurator2
Classification
References
-
us-cert.gov
/ics/advisories/icsa-19-204-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-10972
- NVD CVE-2019-10972
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.