Security readout for executives and security teams
Plain-English summary
This flaw affects Siemens JT2Go and Teamcenter Visualization before V13.2. A malicious PCT file could trigger memory corruption in BMP_loader.dll and may let an attacker run code as the user who opens it.
Executive priority
Prioritize remediation where these Siemens viewers are used for external files or supplier/customer design exchange. Treat this as a workstation code-execution risk, not confirmed active exploitation from the provided evidence.
Technical view
The vulnerable BMP_loader.dll does not properly validate user-supplied data while parsing PCT files, leading to an out-of-bounds write past an allocated structure. The reported impact is code execution in the current process. The weakness maps to CWE-787.
Likely exposure
Exposure is most likely on engineering or manufacturing workstations where JT2Go or Teamcenter Visualization before V13.2 opens PCT content. The provided sources do not state that this is remotely exploitable without user interaction.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. The practical risk is malicious or untrusted file handling, where code execution would occur in the context of the affected application process.
Researcher notes
Severity data and CVSS were not included in the supplied bundle. The key technical detail is CWE-787 out-of-bounds write in BMP_loader.dll during PCT parsing, credited as ZDI-CAN-13403.
Mitigation direction
- Upgrade JT2Go and Teamcenter Visualization to V13.2 or later where applicable.
- Review Siemens SSA-483182 for product-specific remediation guidance.
- Restrict opening PCT files from untrusted sources until affected versions are remediated.
- Apply normal endpoint controls around downloaded or emailed engineering files.
Validation and detection
- Inventory JT2Go and Teamcenter Visualization installations across engineering workstations.
- Confirm installed versions are V13.2 or later.
- Review file-handling workflows for untrusted PCT files.
- Check whether users can open PCT files from email, web downloads, or shared folders.
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-787: 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-34318 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-854/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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.