Security readout for executives and security teams
Plain-English summary
CVE-2019-10972 affects Mitsubishi Electric FR Configurator2 version 1.16S and earlier. A malicious project file can make the application consume CPU and stop responding until restarted. The business risk is disruption to engineering or maintenance workflows, not evidence of system takeover.
Executive priority
Treat as a moderate operational risk for industrial engineering workstations. Prioritize inventory and user-facing controls, then confirm vendor remediation guidance before planning upgrades.
Technical view
The issue is classified as CWE-400 resource exhaustion. The trigger is user interaction: opening a rogue .frc2 project file in affected FR Configurator2 versions. Available source data describes CPU exhaustion and application non-response requiring restart. No CVSS score, patch details, or broader impact are provided in the supplied bundle.
Likely exposure
Exposure is likely limited to organizations using Mitsubishi Electric FR Configurator2 version 1.16S or earlier, especially where staff receive or exchange .frc2 project files from external or untrusted sources.
Exploitation context
The supplied data does not show active exploitation, and the CVE is not marked KEV. Exploitation requires convincing a user to open a rogue project file. The documented outcome is local application denial of service until restart.
Researcher notes
Evidence is sparse. The bundle supports affected product, affected versions, file-based trigger, CWE-400 classification, and denial-of-service outcome. It does not support remote code execution, privilege escalation, active exploitation, or a specific fixed release.
Mitigation direction
- Identify FR Configurator2 installations and versions.
- Do not open untrusted .frc2 project files.
- Check Mitsubishi Electric or CISA guidance for fixed versions or mitigations.
- Restrict project-file intake to trusted channels.
- Educate engineering users about malicious project-file risk.
Validation and detection
- Confirm whether FR Configurator2 is installed.
- Verify installed versions are later than 1.16S where possible.
- Review whether users handle external .frc2 files.
- Check endpoint logs for repeated FR Configurator2 hangs.
- Document compensating controls if no update is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-10972 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.us-cert.gov/ics/advisories/icsa-19-204-01CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
