dbcve.org
Jt2goApplication · Siemens

CVE-2021-34329

HIGH · 7.8 CVSS v3.1 Published 2021-07-13
Fix available
A fix is available. Upgrade to 13.2.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in JT2Go (All versions < V13.2), Solid Edge SE2021 (All Versions < SE2021MP5), Teamcenter Visualization (All versions < V13.2). The plmxmlAdapterSE70.dll library in affected applications lacks proper validation of user-supplied data when parsing PAR files. This could result in an out of bounds write past the fixed-length heap-based buffer. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13427)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A heap-based buffer overflow vulnerability exists in the plmxmlAdapterSE70.dll library used by JT2Go, Solid Edge SE2021, and Teamcenter Visualization. The library fails to properly validate user-supplied data when parsing PAR files, allowing an attacker to write beyond buffer boundaries and potentially execute arbitrary code in the context of the current process.

MitigationApply vendor patches by upgrading JT2Go and Teamcenter Visualization to version V13.2 or later, and Solid Edge SE2021 to SE2021MP5 or later. Until patches are applied, avoid opening untrusted PAR files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jt2goApplication
Affected:< 13.2.0
Solid EdgeWeb browser
Affected:< se2021= se2021
Teamcenter VisualizationApplication
Affected:< 13.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens products
    Check for JT2Go, Solid Edge SE2021, or Teamcenter Visualization installations on the system. Look in common install directories such as C:\Program Files\Siemens or check Program Files/Program Files (x86) for Siemens folders.
    Affected if Any of these three products are installed
  2. Check JT2Go version
    If JT2Go is installed, right-click the JT2Go application in the programs list and select Properties, or check the file version of JT2Go.exe in the installation directory. Compare the version number to 13.2.0.
    Affected if JT2Go version is below 13.2.0
  3. Check Solid Edge version
    If Solid Edge is installed, check the version of the main executable (usually SolidEdge.exe) in the installation folder or view the program properties. Compare against se2021 and verify if MP5 patch has been applied.
    Affected if Solid Edge version is se2021 or earlier (before se2021MP5)
  4. Check Teamcenter Visualization version
    If Teamcenter Visualization is installed, check the version of the visualization components or the main application executable. Compare to version 13.2.0.
    Affected if Teamcenter Visualization version is below 13.2.0
  5. Verify vulnerable DLL exists
    Search for plmxmlAdapterSE70.dll in the installation directories of the affected products. The DLL is the specific component with the overflow vulnerability.
    Affected if The plmxmlAdapterSE70.dll file exists in a Siemens product installation folder
  6. Confirm PAR file parsing capability
    Attempt to open or load a PAR file in the installed product, or verify the product has the capability to import/parse PAR file formats.
    Affected if The product can parse PAR files, which is the attack vector for this vulnerability

A user is affected if they have JT2Go, Solid Edge SE2021, or Teamcenter Visualization installed with versions below the patched releases (13.2.0 for JT2Go/Teamcenter Visualization, se2021MP5 for Solid Edge) and the plmxmlAdapterSE70.dll component is present and capable of parsing PAR files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 13.2.0 or later
Fixed in 13.2.0
Interim mitigation

Apply vendor patches by upgrading JT2Go and Teamcenter Visualization to version V13.2 or later, and Solid Edge SE2021 to SE2021MP5 or later. Until patches are applied, avoid opening untrusted PAR files from unknown sources.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data