Code execution via out-of-bounds JT parsing
Published Aug 8, 2023 · Updated Oct 11, 2024
Out-of-bounds read in Siemens JT Open before 11.4 and JT Utilities before 13.4 allows attackers to execute code via crafted JT files. The JT parsers read past the end of an allocated structure while processing malformed file data; no finer-grained code locus is public. A user must open the crafted file, after which code runs with the affected process's privileges and the application can also crash.
Summary
What happened
Out-of-bounds read in Siemens JT Open before 11.4 and JT Utilities before 13.4 allows attackers to execute code via crafted JT files. The JT parsers read past the end of an allocated structure while processing malformed file data; no finer-grained code locus is public. A user must open the crafted file, after which code runs with the affected process's privileges and the application can also crash.
The record
- CVE
- CVE-2023-30796
- Published
- Aug 8, 2023
- Updated
- Oct 11, 2024
- Vendor
- Siemens
- Product
- JT Utilities
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Oct 11, 2024Record 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=All versions < V13.4
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.
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