Code execution via uninitialized JT parser pointer
Published Oct 11, 2022 · Updated May 20, 2025
Uninitialized pointer access in Siemens JTTK and Simcenter Femap allows remote attackers to execute code through a crafted JT file. The JT file parser accesses a pointer without properly initializing it, which can crash the application or redirect execution within its process. Exploitation requires a user to open a malicious JT file; affected releases are JTTK before 11.1.1.0 and Femap 2022.1 before 2022.1.3 or 2022.2 before 2022.2.2.
Summary
What happened
Uninitialized pointer access in Siemens JTTK and Simcenter Femap allows remote attackers to execute code through a crafted JT file. The JT file parser accesses a pointer without properly initializing it, which can crash the application or redirect execution within its process. Exploitation requires a user to open a malicious JT file; affected releases are JTTK before 11.1.1.0 and Femap 2022.1 before 2022.1.3 or 2022.2 before 2022.2.2.
The record
- CVE
- CVE-2022-41851
- Published
- Oct 11, 2022
- Updated
- May 20, 2025
- Vendor
- Siemens
- Product
- JT Open Toolkit
- Classifications
- CWE-824, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- May 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 < V11.1.1.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