dbcve.org
Jt2goApplication · Siemens

CVE-2020-27003

HIGH · 7.8 CVSS v3.1 Published 2021-02-09
Fix available
A fix is available. Upgrade to 13.1.0.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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.1.0.1), Teamcenter Visualization (All versions < V13.1.0.1). Affected applications lack proper validation of user-supplied data when parsing TIFF files. This could lead to pointer dereferences of a value obtained from untrusted source. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-12158)

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

This is a heap-based pointer dereference vulnerability in Siemens JT2Go and Teamcenter Visualization applications. The affected software fails to properly validate user-supplied data when parsing TIFF image files, allowing an attacker to control a pointer value derived from an untrusted source. This can be exploited to achieve arbitrary code execution in the context of the current process by convincing a user to open a malicious TIFF file.

MitigationUpgrade JT2Go and Teamcenter Visualization to version V13.1.0.1 or later to obtain the patch. Until patched, avoid opening TIFF files from untrusted sources.

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.1.0.1
Teamcenter VisualizationApplication
Affected:< 13.1.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 visualization product
    Check for JT2Go or Teamcenter Visualization installation. On Windows, look in Program Files for 'Siemens\JT2Go' or 'Siemens\Teamcenter Visualization'. The product name is typically visible in the application GUI title bar when launched.
    Affected if Neither product is installed - not affected. Either product is installed - proceed to version check.
  2. Determine JT2Go version
    If JT2Go is installed, find the version by right-clicking the executable (typically in C:\Program Files\Siemens\JT2Go\), selecting Properties, and checking the Details tab for File Version or Product Version.
    Affected if Version number is less than 13.1.0.1 - vulnerable.
  3. Determine Teamcenter Visualization version
    If Teamcenter Visualization is installed, find the version by right-clicking the main executable (such as TcVis.exe or the visualization component), selecting Properties, and checking the Details tab for File Version or Product Version.
    Affected if Version number is less than 13.1.0.1 - vulnerable.
  4. Confirm TIFF file handling capability
    Check if the installed software can open or process TIFF files. This is a built-in capability of these visualization products - they are designed to handle various image formats including TIFF for 3D visualization workflows.
    Affected if The product can open or render TIFF files and version is below 13.1.0.1 - vulnerable and likely exploitable if malicious TIFF is opened.

You are affected if either JT2Go or Teamcenter Visualization is installed with a version number lower than 13.1.0.1, as the vulnerability exists in the TIFF file parsing component of these versions.

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.1.0.1 or later
Fixed in 13.1.0.1
Interim mitigation

Upgrade JT2Go and Teamcenter Visualization to version V13.1.0.1 or later to obtain the patch. Until patched, avoid opening TIFF files from untrusted sources.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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