CVE-2020-26980
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 · uneditedA vulnerability has been identified in JT2Go (All versions < V13.1.0), Teamcenter Visualization (All versions < V13.1.0). Affected applications lack proper validation of user-supplied data when parsing JT files. A crafted JT file could trigger a type confusion condition. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-11881)
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 confidenceJT2Go and Teamcenter Visualization fail to validate user-supplied data when parsing JT (Jupiter Tessellation) CAD files, allowing a type confusion condition to be triggered. A specially crafted JT file can cause memory corruption leading to arbitrary code execution in the context of the current process.
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< 13.1.0< 13.1.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Siemens JT2Go is installedLook for JT2Go in the Windows Start Menu, or check for the installation directory (typically C:\Program Files\Siemens\JT2Go or C:\Program Files (x86)\Siemens\JT2Go)Affected if JT2Go is present on the system and the version is below 13.1.0
-
Check if Siemens Teamcenter Visualization is installedLook for Teamcenter Visualization in the Windows Start Menu, or check common installation paths under C:\Program Files\Siemens\Affected if JT2Go is present on the system and the version is below 13.1.0 or Teamcenter Visualization is present and below 13.1.0
-
Verify installed version of JT2GoOpen JT2Go and go to Help > About, or right-click the JT2Go executable in the installation folder, select Properties, and check the File Version fieldAffected if The reported version number is lower than 13.1.0
-
Verify installed version of Teamcenter VisualizationOpen Teamcenter Visualization and check the About section, or right-click the executable (typically tcvis.exe or similar) in the installation folder and check the File VersionAffected if The reported version number is lower than 13.1.0
-
Confirm JT file parsing capability is accessibleAttempt to open a JT file in the installed application, or check if the application can import/load JT files through its file menuAffected if The application can successfully load and parse JT files, meaning the vulnerable parsing code is in use
You are affected if either JT2Go or Teamcenter Visualization is installed with a version number below 13.1.0 and the application can be used to open or parse JT files.
Generated from the published advisory. Verify against your own configuration.
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 data13.1.0
Upgrade JT2Go and Teamcenter Visualization to version V13.1.0 or later. Until then, exercise extreme caution with untrusted JT files and consider restricting file handling to trusted sources.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26980 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26980 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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