dbcve.org
Jt2goApplication · Siemens

CVE-2021-34323

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), Teamcenter Visualization (All versions < V13.2). The Jt981.dll library in affected applications lacks proper validation of user-supplied data when parsing JT files. This could result in an out of bounds write past the end of an allocated structure. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13419)

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 buffer overflow vulnerability exists in the Jt981.dll library used by JT2Go and Teamcenter Visualization applications. When parsing JT files, the library fails to properly validate user-supplied data, leading to an out-of-bounds write beyond allocated memory boundaries. This allows an attacker to achieve code execution within the context of the current user process.

MitigationUpgrade JT2Go and Teamcenter Visualization to version 13.2 or later to obtain the patched Jt981.dll library. If immediate patching is not possible, restrict processing of untrusted JT files and implement application sandboxing as compensating controls.

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
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. Check if JT2Go is installed and its version
    Locate the JT2Go installation directory (typically C:\Program Files\Siemens\JT2Go or similar) and locate the executable file. Right-click on JT2Go.exe, select Properties, and check the File Version or Product Version field. Alternatively, open a command prompt and run: dir /s "C:\Program Files\Siemens\JT2Go\JT2Go.exe" to find the installation path, then check version via Properties.
    Affected if The installed version is below 13.2.0
  2. Check if Teamcenter Visualization is installed and its version
    Locate the Teamcenter Visualization installation directory (typically C:\Program Files\Siemens\Teamcenter<version>\Visualization or C:\Program Files\Siemens\Teamcenter Visualization). Find the main executable and check its File Version or Product Version in Properties. Alternatively, check in Windows Programs and Features (Control Panel > Programs > Programs and Features) for the installed version.
    Affected if The installed version is below 13.2.0
  3. Identify the Jt981.dll file version
    Navigate to the installation directory of either JT2Go or Teamcenter Visualization and locate Jt981.dll. Right-click on the file, select Properties, and check the File Version information. The DLL is typically found in the bin or main application folder.
    Affected if The DLL file version is present and corresponds to an application version below 13.2.0
  4. Verify the vulnerability trigger condition
    Confirm that the application is used to open or process JT files. The vulnerability is triggered when the affected version of Jt981.dll parses a specially crafted malicious JT file. Check recent usage or access to untrusted JT files.
    Affected if A vulnerable version (below 13.2.0) of the software is installed AND the application is used to process JT files, especially from untrusted sources

A system is affected if JT2Go or Teamcenter Visualization version is below 13.2.0, the Jt981.dll library from a vulnerable version is present, and the application is used to parse JT 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

Upgrade JT2Go and Teamcenter Visualization to version 13.2 or later to obtain the patched Jt981.dll library. If immediate patching is not possible, restrict processing of untrusted JT files and implement application sandboxing as compensating controls.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34323 — 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-34323 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