dbcve.org
Jt2goApplication · Siemens

CVE-2021-34291

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

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 Gif_loader.dll library of JT2Go and Teamcenter Visualization. The library fails to properly validate user-supplied data when parsing GIF files, allowing an attacker to trigger an out-of-bounds write past the end of an allocated buffer. This memory corruption can be weaponized to achieve arbitrary code execution in the context of the current process.

MitigationUpdate JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched Gif_loader.dll library. Until patching is possible, avoid opening untrusted GIF files with affected applications.

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 Siemens products
    Check system for installed JT2Go or Teamcenter Visualization applications. On Windows, this can be done via Add/Remove Programs, or by searching for the application executables in typical installation directories such as C:\Program Files\Siemens or C:\Program Files (x86)\Siemens.
    Affected if Either JT2Go or Teamcenter Visualization is installed on the system.
  2. Determine JT2Go version
    If JT2Go is installed, locate its executable (typically JT2Go.exe) and check the file version. Right-click the file, select Properties, and view the Details tab. Alternatively, run 'wmic product where "name like 'JT2Go'" get version' or use the application's About/Help menu if accessible.
    Affected if The installed JT2Go version is any version prior to 13.2.0.
  3. Determine Teamcenter Visualization version
    If Teamcenter Visualization is installed, locate its executable (commonly TcVisualization.exe or similar) and check the file version via Properties Details tab. You may also check the installation directory for version information or use 'wmic product where "name like 'Teamcenter'" get version'.
    Affected if The installed Teamcenter Visualization version is any version prior to 13.2.0.
  4. Locate Gif_loader.dll library
    Search for Gif_loader.dll in the application installation directories of JT2Go or Teamcenter Visualization. The file is typically found in the bin or program directory alongside the main executable. Note the file path for version checking.
    Affected if Gif_loader.dll exists in the JT2Go or Teamcenter Visualization installation directory.
  5. Check Gif_loader.dll version if accessible
    If Gif_loader.dll is found, right-click the file, select Properties, and view the File version field on the Details tab. Compare this version against the version bundled with the V13.2.0 patch.
    Affected if The Gif_loader.dll file version is older than the version included in V13.2.0, or the version cannot be determined and the product version is below 13.2.0.

A system is affected if either JT2Go or Teamcenter Visualization is installed with a version number lower than 13.2.0, as this indicates the vulnerable Gif_loader.dll library is present.

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 patched Gif_loader.dll library. Until patching is possible, avoid opening untrusted GIF files with affected applications.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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