Code execution via out-of-bounds JT structure write
Published Dec 14, 2021 · Updated Aug 4, 2024
Out-of-bounds write in Siemens JT Utilities before 13.1.1.0 and JT Open Toolkit before 11.1.1.0 allows attackers to execute code. The JTTK parser writes past the end of an allocated structure when processing a specially crafted JT file. Exploitation requires a user to open the file, and resulting code runs in the current process context.
Summary
What happened
Out-of-bounds write in Siemens JT Utilities before 13.1.1.0 and JT Open Toolkit before 11.1.1.0 allows attackers to execute code. The JTTK parser writes past the end of an allocated structure when processing a specially crafted JT file. Exploitation requires a user to open the file, and resulting code runs in the current process context.
The record
- CVE
- CVE-2021-44430
- Published
- Dec 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Siemens
- Product
- JT Utilities
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.1.1.0
What conditions does exploitation require?
What is affected?
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