Code execution via stack overflow in JT parser
Published Feb 14, 2023 · Updated Mar 20, 2025
Stack overflow in affected Siemens JT Open Toolkit, JT Utilities, and Parasolid releases allows local users to execute code via a JT file. The products' JT parsers overflow a stack buffer while processing specially crafted file data; Siemens has not disclosed the precise parser routine or malformed field. Exploitation requires a user to open the file, after which attacker-controlled code runs with the privileges of the current process or the application crashes.
Summary
What happened
Stack overflow in affected Siemens JT Open Toolkit, JT Utilities, and Parasolid releases allows local users to execute code via a JT file. The products' JT parsers overflow a stack buffer while processing specially crafted file data; Siemens has not disclosed the precise parser routine or malformed field. Exploitation requires a user to open the file, after which attacker-controlled code runs with the privileges of the current process or the application crashes.
The record
- CVE
- CVE-2022-47936
- Published
- Feb 14, 2023
- Updated
- Mar 20, 2025
- Vendor
- Siemens
- Product
- JT Utilities
- Classifications
- CWE-121, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2023CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=All versions < V13.2.3.0
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