Security readout for executives and security teams
Plain-English summary
A vulnerable Screen Creator Advance 2 workstation can be compromised if a user opens a malicious project file. The issue is in project file parsing, not a remotely exposed service. Business urgency is highest where this software handles files from customers, vendors, or shared engineering environments.
Executive priority
Treat as high priority for affected engineering environments, especially if project files cross organizational boundaries. It is not described as internet-exploitable, but successful social engineering could lead to code execution or sensitive information exposure on engineering systems.
Technical view
CVE-2023-22347 is a CWE-125 out-of-bounds read in JTEKT Screen Creator Advance 2 Ver.0.1.1.4 Build01 and earlier. The parser cannot verify the end of data while processing file structure information. Sources state a crafted project file may cause information disclosure and/or arbitrary code execution.
Likely exposure
Exposure is limited to systems running Screen Creator Advance 2 Ver.0.1.1.4 Build01 or earlier. Risk is concentrated on engineering workstations where users open project files from external parties, shared repositories, removable media, or email attachments.
Exploitation context
The bundle does not indicate CISA KEV listing or active exploitation. Exploitation requires user interaction: a Screen Creator Advance 2 user must open a specially crafted project file. No exploit maturity, public proof of concept, or in-the-wild activity is provided.
Researcher notes
The key exposure condition is vulnerable file parsing plus user-assisted opening of a crafted project file. The source bundle does not provide patch version details, exploit samples, or active exploitation evidence. Validate affected builds and follow vendor/JVN remediation guidance.
Mitigation direction
- Inventory Screen Creator Advance 2 installations and versions.
- Check JTEKT and JVN guidance for update or mitigation details.
- Avoid opening project files from untrusted or unexpected sources.
- Handle external project files in isolated engineering workstations where practical.
- Apply endpoint controls around downloaded or emailed project files.
Validation and detection
- Confirm whether any host runs Ver.0.1.1.4 Build01 or earlier.
- Review how project files enter engineering workflows.
- Check whether users receive project files from external parties.
- Verify vendor guidance has been reviewed and applied.
- Confirm endpoint logging covers file-open activity for this application.
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-22347 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.