Jt2goApplication · Siemens

CVE-2021-34312

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

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

The Tiff_loader.dll library in JT2Go and Teamcenter Visualization lacks proper validation of user-supplied data when parsing TIFF files, leading to an out-of-bounds write past a fixed-length heap-based buffer. An attacker can exploit this by tricking a user into opening a specially crafted malicious TIFF file, achieving code execution in the context of the current process.

MitigationUpgrade JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched Tiff_loader.dll library.

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. Identify installed product and version
    Open the application and navigate to Help > About, or locate the application executable (JT2Go.exe or Teamcenter Visualization executable) and check its file properties for version information
    Affected if The version shown is below 13.2.0 (for example, 13.1.x or earlier)
  2. Locate Tiff_loader.dll in the application directory
    Search the installation folder of JT2Go or Teamcenter Visualization for a file named Tiff_loader.dll. Right-click the file and select Properties to view its version information
    Affected if The DLL exists in the installation directory, indicating the vulnerable component is present
  3. Check Tiff_loader.dll file version
    In the DLL's Properties window, look at the File Version field on the Details tab
    Affected if The file version is not V13.2.0 or later, or no version information is available for the DLL
  4. Verify application can process TIFF files
    Attempt to open any TIFF file through the application, or check if TIFF file associations are registered
    Affected if The application can load TIFF files, meaning the vulnerable parsing code path is reachable
  5. Compare against known affected versions
    Document the exact version numbers found for both the main application and Tiff_loader.dll, then compare them to the vulnerable range (anything below 13.2.0)
    Affected if Either the application version or the DLL version is below 13.2.0, indicating the vulnerable code is present

If JT2Go or Teamcenter Visualization is installed with a version below 13.2.0 and the Tiff_loader.dll component is present, the environment is affected by this CVE.

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 V13.2 or later to obtain the patched Tiff_loader.dll library.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-34312 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