Security readout for executives and security teams
Plain-English summary
Siemens JT2Go and Teamcenter Visualization before V13.2 can mishandle a crafted JT file. Opening such a file could let an attacker run code as the user running the application. This matters where engineering, manufacturing, or supply-chain teams exchange JT files from outside parties.
Executive priority
Prioritize remediation for engineering and manufacturing users who open externally supplied JT files. Business urgency is high where JT exchange is common, because compromise could occur through normal file-review workflows.
Technical view
The Jt981.dll parser lacks proper validation of user-supplied data before further free operations while parsing JT files. The CVE maps to CWE-416, use-after-free, and ZDI reports code execution in the current process context. The bundle does not provide CVSS scoring.
Likely exposure
Exposure is likely limited to endpoints or servers where Siemens JT2Go or Teamcenter Visualization versions earlier than V13.2 parse JT files, especially files received from suppliers, customers, or shared project repositories.
Exploitation context
The provided sources support code execution through malicious JT file parsing. The CVE is not listed as KEV in the bundle, and no cited source here states active exploitation in the wild.
Researcher notes
The core issue is a use-after-free in Jt981.dll during JT parsing. Evidence in the bundle identifies affected products and pre-V13.2 versions but does not include CVSS, active exploitation evidence, or detailed vendor mitigations beyond the fixed-version boundary.
Mitigation direction
- Upgrade JT2Go and Teamcenter Visualization to V13.2 or later.
- Review Siemens SSA-483182 for product-specific remediation guidance.
- Restrict opening JT files from untrusted or external sources until remediated.
- Run affected viewers with least-privilege user accounts where operationally possible.
Validation and detection
- Inventory installed JT2Go and Teamcenter Visualization versions.
- Confirm no affected installation remains below V13.2.
- Review workflows that accept JT files from external parties.
- Check EDR or endpoint logs for crashes around JT file handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-34330 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://cert-portal.siemens.com/productcert/pdf/ssa-483182.pdfCVE reference · x_refsource_MISC
- https://www.zerodayinitiative.com/advisories/ZDI-21-868/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.