Security readout for executives and security teams
Plain-English summary
This flaw affects JTEKT Screen Creator Advance 2 project-file handling. If a user opens a malicious project file, the software may read past expected data, potentially exposing information or enabling code execution on that workstation.
Executive priority
Prioritize remediation for OT or engineering teams that exchange project files externally. The business risk is workstation compromise through normal project-file handling, with possible confidentiality, integrity, and availability impact.
Technical view
CVE-2023-22349 is a CWE-125 out-of-bounds read in Screen Creator Advance 2 Ver.0.1.1.4 Build01 and earlier. It occurs when screen management information is processed without verifying the end of data. CVSS 3.1 is 7.8: local attack, low complexity, no privileges, user interaction required, high impact.
Likely exposure
Exposure is limited to environments running the affected Screen Creator Advance 2 versions, especially engineering or operational workstations that open project files from partners, vendors, email, removable media, or shared repositories.
Exploitation context
The provided sources describe malicious project-file opening as the attack path. The bundle marks KEV as false and provides no evidence of active exploitation. Treat this as a file-ingestion risk, not a remotely reachable network service issue.
Researcher notes
Evidence is sufficient for affected product, version range, weakness class, trigger, and CVSS. The public bundle does not provide exploit details, active exploitation evidence, or a named fixed version, so remediation should be anchored to JTEKT/JVN advisories.
Mitigation direction
- Identify all Screen Creator Advance 2 installations and installed versions.
- Check JTEKT and JVN guidance for the vendor-supported fix or mitigation.
- Restrict opening project files to trusted, validated sources.
- Quarantine externally received project files before engineering workstation use.
- Use endpoint controls to monitor unexpected child processes from the application.
Validation and detection
- Confirm whether installed versions are Ver.0.1.1.4 Build01 or earlier.
- Review engineering workflows for external project-file intake.
- Verify vendor guidance has been applied where affected installations exist.
- Check email, file-share, and removable-media logs for suspicious project files.
- Document compensating controls if vendor remediation is unavailable.
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-125: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-22349 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.electronics.jtekt.co.jp/en/topics/202302035233/CVE reference
- https://www.electronics.jtekt.co.jp/jp/topics/2023020313454/CVE reference
- https://jvn.jp/en/vu/JVNVU98917488/CVE reference
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.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.