Code execution via unchecked project-file size field
Published Apr 11, 2023 · Updated Feb 11, 2025
Memory corruption in JTEKT Screen Creator Advance 2 0.1.1.4 Build01A and earlier allows attackers to execute code via a crafted project file. The control-information reader trusts a project-file size field without validating it against the memory buffer, enabling out-of-bounds reads and writes. Exploitation requires a user to open the file and can disclose process-accessible information or execute code in that user's context.
Summary
What happened
Memory corruption in JTEKT Screen Creator Advance 2 0.1.1.4 Build01A and earlier allows attackers to execute code via a crafted project file. The control-information reader trusts a project-file size field without validating it against the memory buffer, enabling out-of-bounds reads and writes. Exploitation requires a user to open the file and can disclose process-accessible information or execute code in that user's context.
The record
- CVE
- CVE-2023-25755
- Published
- Apr 11, 2023
- Updated
- Feb 11, 2025
- Vendor
- JTEKT ELECTRONICS CORPORATION
- Product
- Screen Creator Advance 2
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Ver.0.1.1.4 Build01A and earlier
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo