Security readout for executives and security teams
Plain-English summary
CVE-2022-33317 affects Mitsubishi Electric industrial monitoring software. If a user opens a malicious monitoring screen file, an unauthenticated attacker could cause malicious script code to run on that system. The impact can include loss of confidentiality, integrity, and availability on affected workstations.
Executive priority
Treat as high priority where affected Mitsubishi monitoring software supports operational technology. The vulnerability needs user interaction, but successful exploitation could affect critical workstation trust and operations. Prioritize inventory and vendor-guided remediation over broad emergency assumptions.
Technical view
The issue is CWE-829: inclusion of functionality from an untrusted control sphere. Affected GENESIS64, ICONICS Suite, and MC Works64 versions may execute malicious script code embedded in a monitoring screen file. CVSS 3.1 is 7.8 with local attack vector and required user interaction.
Likely exposure
Exposure is most likely in OT or ICS environments using affected Mitsubishi GENESIS64, ICONICS Suite, or MC Works64 monitoring software, especially where screen files are exchanged, imported, or opened by operators or engineers.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. The attack requires persuading a user to load a malicious monitoring screen file, so phishing, file sharing, or compromised engineering workflows are plausible contexts.
Researcher notes
Evidence is strong for affected products, vulnerability class, and impact scoring. The supplied bundle does not include patch-version details, exploit indicators, or active exploitation claims, so remediation should be tied directly to current vendor advisory guidance.
Mitigation direction
- Identify all Mitsubishi GENESIS64, ICONICS Suite, and MC Works64 installations and versions.
- Check Mitsubishi, CISA, and JVN guidance for supported updates or mitigations.
- Restrict opening monitoring screen files to trusted, verified sources.
- Limit file transfer paths into engineering and operator workstations.
- Use least privilege and segmentation around affected OT workstations.
Validation and detection
- Compare installed product versions against the affected version ranges in the CVE record.
- Review whether users can import or open monitoring screen files from untrusted locations.
- Confirm vendor guidance has been reviewed for each affected product line.
- Check OT workstations for controls limiting scripts or untrusted project files.
- Document compensating controls where upgrades are not immediately possible.
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-829: 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-2022-33317 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.mitsubishielectric.com/en/psirt/vulnerability/pdf/2022-008_en.pdfCVE reference · vendor-advisory
- https://jvn.jp/vu/JVNVU96480474/index.htmlCVE reference · government-resource
- https://www.cisa.gov/news-events/ics-advisories/icsa-22-202-04CVE reference · government-resource
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.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.