Jt2goApplication · Siemens

CVE-2021-34303

MEDIUM · 5.5 CVSS v3.1 Published 2021-07-13
Fix available
A fix is available. Upgrade to 13.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
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 read past the end of an allocated buffer. An attacker could leverage this vulnerability to leak information in the context of the current process. (ZDI-CAN-13198)

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 fails to properly validate user-supplied data when parsing TIFF files, leading to an out-of-bounds read past the end of an allocated buffer. This allows an attacker to leak sensitive information from process memory by tricking a user into opening a maliciously crafted TIFF file.

MitigationUpgrade JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched Tiff_Loader.dll library that properly validates TIFF file data.

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
None
Availability
None

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

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
    Check if Siemens JT2Go or Teamcenter Visualization is installed on the system by reviewing installed programs or locating the application executable (JT2Go.exe or Teamcenter Visualization binaries)
    Affected if Either product is installed and the version is below 13.2.0
  2. Check product version
    Right-click the executable (JT2Go.exe or the Teamcenter Visualization application), select Properties, and review the File Version or Product Version field
    Affected if The reported version number is lower than 13.2.0 (for example, 13.1.x, 13.0.x, or earlier)
  3. Locate Tiff_Loader.dll
    Search for Tiff_Loader.dll within the product installation directory, typically found in the bin or application folder where the main executable resides
    Affected if Tiff_Loader.dll exists in the product directory and its file version is not the patched V13.2 release
  4. Verify TIFF processing capability
    Open the application and confirm whether it can load or import TIFF image files, or check file association settings for .tiff/.tif extensions
    Affected if The application is configured to process TIFF files and can be triggered to parse a user-supplied TIFF file

The environment is affected if JT2Go or Teamcenter Visualization is installed with a version lower than 13.2.0 and the vulnerable Tiff_Loader.dll is present, allowing a malicious TIFF file to trigger an out-of-bounds read.

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 that properly validates TIFF file data.

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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