Security readout for executives and security teams
Plain-English summary
This vulnerability affects JTEKT Screen Creator Advance 2. If a user opens a specially crafted project file, the software may corrupt memory, potentially exposing information or allowing code execution. The business risk is highest where engineering staff exchange project files externally.
Executive priority
Treat this as a high-priority workstation exposure for teams using the affected JTEKT software. It is not described as remotely exploitable over the network, but malicious project files can create serious confidentiality, integrity, and availability impact.
Technical view
CVE-2023-22345 is a CWE-787 out-of-bounds write in Screen Creator Advance 2 Ver.0.1.1.4 Build01 and earlier. The issue is linked to missing error handling for out-of-specification errors. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, user interaction required, high CIA impact.
Likely exposure
Exposure is limited to organizations using Screen Creator Advance 2 Ver.0.1.1.4 Build01 or earlier. The attack path is project-file handling by a user, so engineering workstations and file exchange workflows are the likely risk points.
Exploitation context
The source bundle says exploitation requires a user to open a specially crafted project file. KEV status is false, and the provided sources do not report active exploitation. Evidence is insufficient to claim public exploitation or weaponized tooling.
Researcher notes
The record identifies an out-of-bounds write caused by insufficient error handling when out-of-specification errors are detected. The source bundle does not provide patch details, proof-of-concept status, affected platforms beyond the product/version, or indicators of compromise.
Mitigation direction
- Identify installations of Screen Creator Advance 2 and record exact versions.
- Check JTEKT and JVN guidance for fixed versions or official workarounds.
- Restrict opening project files from untrusted or unexpected sources.
- Handle project files through controlled intake and malware scanning workflows.
- Prioritize upgrades or compensating controls on engineering workstations.
Validation and detection
- Inventory endpoints for Screen Creator Advance 2 Ver.0.1.1.4 Build01 or earlier.
- Review whether users receive project files from external parties.
- Confirm vendor advisory status before declaring remediation complete.
- Check security telemetry for suspicious activity after project-file opens.
- Verify vulnerable versions are upgraded, removed, or otherwise controlled.
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-787: 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-22345 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 Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.