Process-memory disclosure via out-of-bounds JT parsing
Published Dec 14, 2021 · Updated Aug 4, 2024
Out-of-bounds read in Siemens JT Utilities before 13.1.1.0 and JT Open Toolkit before 11.1.1.0 allows attackers to disclose process memory. The JTTK parser reads past the end of an allocated buffer while processing crafted JT data; Siemens has not identified the responsible routine or field. Exploitation requires a user to open an attacker-supplied JT file, exposing memory in the affected process without modifying data.
Summary
What happened
Out-of-bounds read in Siemens JT Utilities before 13.1.1.0 and JT Open Toolkit before 11.1.1.0 allows attackers to disclose process memory. The JTTK parser reads past the end of an allocated buffer while processing crafted JT data; Siemens has not identified the responsible routine or field. Exploitation requires a user to open an attacker-supplied JT file, exposing memory in the affected process without modifying data.
The record
- CVE
- CVE-2021-44439
- Published
- Dec 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Siemens
- Product
- JT Utilities
- Classifications
- CWE-125, 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.
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