CVE-2020-28394
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.1), Teamcenter Visualization (All versions < V13.1.0.1). Affected applications lack proper validation of user-supplied data when parsing of RAS files. This could result in a memory access past the end of an allocated buffer. An attacker could leverage this vulnerability to access data in the context of the current process. (ZDI-CAN-12283)
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 properly validate user-supplied data when parsing RAS files, leading to an out-of-bounds memory read past the end of an allocated buffer. This allows an attacker to access data in the context of the current process via a specially crafted RAS file.
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.1< 13.1.0.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify which affected product is installedCheck for Siemens JT2Go or Teamcenter Visualization in the system. Look in Program Files for 'Siemens\JT2Go' or 'Siemens\Teamcenter Visualization' folders, or check the Windows Registry under HKLM\SOFTWARE\Siemens\ for these products.Affected if Either JT2Go or Teamcenter Visualization is installed on the system.
-
Determine the installed version of JT2GoLocate the JT2Go executable (typically at C:\Program Files\Siemens\JT2Go\JT2Go.exe), right-click and select Properties, or run 'wmic product get name,version' to query installed Siemens software.Affected if The version number displayed is lower than 13.1.0.1.
-
Determine the installed version of Teamcenter VisualizationLocate the Teamcenter Visualization executable (commonly at C:\Program Files\Siemens\Teamcenter Visualization\bin\), check the file properties, or query via 'wmic product' for Teamcenter Visualization.Affected if The version number displayed is lower than 13.1.0.1.
-
Verify RAS file parsing has been usedSearch the system for .ras files that have been opened recently. Check recent documents, temporary folders, or the application's recent files list. On Windows, examine the jump lists or recent items in the Start menu for RAS file access.Affected if Any .ras files have been opened or processed by the affected software.
The system is affected if either JT2Go or Teamcenter Visualization is installed with a version lower than 13.1.0.1 and RAS files have been processed.
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.1
Update JT2Go and Teamcenter Visualization to version V13.1.0.1 or later, which contains the fix for proper validation of RAS file parsing.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28394 — 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-28394 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