Application crash via crafted XML file
Published Jul 9, 2024 · Updated Aug 27, 2025
Null pointer dereference in Siemens JT and Teamcenter products allows attackers to crash affected applications via crafted XML files. Siemens identifies the XML parser as the affected locus but has not published the specific routine or malformed structure that produces the null pointer. Exploitation requires a user to open an attacker-supplied XML file and causes an application-level service interrupt.
Summary
What happened
Null pointer dereference in Siemens JT and Teamcenter products allows attackers to crash affected applications via crafted XML files. Siemens identifies the XML parser as the affected locus but has not published the specific routine or malformed structure that produces the null pointer. Exploitation requires a user to open an attacker-supplied XML file and causes an application-level service interrupt.
The record
- CVE
- CVE-2024-37996
- Published
- Jul 9, 2024
- Updated
- Aug 27, 2025
- Vendor
- Siemens
- Product
- PLM XML SDK
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=0 <V7.1.0.014
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.
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