dbcve.org
Jt2goApplication · Siemens

CVE-2021-34311

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 Mono_loader.dll library in affected applications lacks proper validation of user-supplied data when parsing J2K 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-13352)

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

Buffer overflow vulnerability in Mono_loader.dll when parsing J2K (JPEG 2000) files due to insufficient validation of user-supplied data, leading to out-of-bounds write past allocated structure boundaries and potential arbitrary code execution in current process context.

MitigationUpdate JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the vendor patch; avoid opening untrusted J2K files until patched.

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 Siemens Jt2go is installed
    Look for Jt2go installation directory (typically in Program Files or Program Files (x86)) or check Windows Registry under HKLM\SOFTWARE\Siemens\JT2Go or HKLM\SOFTWARE\WOW6432Node\Siemens\JT2go for the installation path.
    Affected if Jt2go is found with a version lower than 13.2.0
  2. Check if Siemens Teamcenter Visualization is installed
    Look for Teamcenter Visualization installation (common paths: Program Files\Siemens\Teamcenter<version>\Visualization or check Windows Registry under HKLM\SOFTWARE\Siemens\Teamcenter Visualization for install path.
    Affected if Teamcenter Visualization is found with a version lower than 13.2.0
  3. Determine installed version of Jt2go or Teamcenter Visualization
    Open the application's About dialog, check the executable file properties (right-click on Jt2go.exe or Visualization.exe, go to Details tab for File Version), or query the Windows Registry for the Version value under the product's registry key.
    Affected if Version returned is empty, missing, or shows a number less than 13.2.0
  4. Locate Mono_loader.dll in the installation
    Navigate to the installation bin folder (e.g., <install_dir>\bin\) and search for Mono_loader.dll, or use Windows File Explorer search within the installation directory.
    Affected if Mono_loader.dll exists in the product's installation folder
  5. Verify J2K file handling capability is present
    Check if the installation includes J2K-related file readers or codecs. Look for files with .j2k, .jp2 extensions in the bin folder, or check if the application can open or import JPEG 2000 files (attempt to open a sample J2K file or check file association settings).
    Affected if The application can parse or import J2K/JPEG 2000 files

A user is affected if either Siemens Jt2go or Teamcenter Visualization is installed with a version lower than 13.2.0 and the Mono_loader.dll component is present to handle J2K file parsing.

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

Update JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the vendor patch; avoid opening untrusted J2K files until patched.

Fix this in Jt2go Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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