Application crash via race-driven premature object release
Published Jul 13, 2021 · Updated Aug 3, 2024
NULL pointer dereference in Siemens JT Utilities before 13.0.2.0 allows attackers to crash the application via a crafted JT file. A race during JT parsing releases an object before a later operation uses it, producing a NULL pointer dereference. Exploitation requires a user to open the crafted file, and the reported consequence is an application crash rather than code execution.
Summary
What happened
NULL pointer dereference in Siemens JT Utilities before 13.0.2.0 allows attackers to crash the application via a crafted JT file. A race during JT parsing releases an object before a later operation uses it, producing a NULL pointer dereference. Exploitation requires a user to open the crafted file, and the reported consequence is an application crash rather than code execution.
The record
- CVE
- CVE-2021-33715
- Published
- Jul 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Siemens
- Product
- JT Utilities
- Classifications
- CWE-476, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.0.2.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