CVE-2020-27004
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 CGM 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-12163)
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 confidenceBuffer overread vulnerability in CGM file parsing in JT2Go and Teamcenter Visualization applications. Insufficient validation of user-supplied data during CGM file parsing leads to memory access beyond allocated buffer boundaries, allowing an attacker to read data 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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify which affected product is installedCheck for presence of JT2Go or Teamcenter Visualization on the system. JT2Go typically installs to Program Files\Siemens\JT2Go\. Teamcenter Visualization installs under its product directory. Use Windows Explorer or command 'dir /s /b "C:\Program Files*\Siemens\JT2Go.exe"' to locate JT2Go, or check for Teamcenter Visualization executables in the Siemens installation directory.Affected if Either JT2Go or Teamcenter Visualization application is installed on the system
-
Determine the installed version of the productRight-click the main executable (JT2Go.exe or the Teamcenter Visualization application binary) and select Properties, then view the Details tab to see the File Version. Alternatively, check the Windows registry under HKLM\SOFTWARE\Siemens\JT2Go\ for the Version value, or use PowerShell: (Get-Item "C:\Program Files\Siemens\JT2Go\JT2Go.exe").VersionInfo.FileVersionAffected if The reported version is less than 13.1.0.1 (for example, 13.0.x, 12.x, or earlier)
-
Confirm CGM file parsing capability is presentCheck that the application has native CGM import or parsing capability. This is typically built into the core application. Verify CGM-related DLLs or resources exist in the installation directory (such as cgmlib, cgmparser, or similar files), or check if the application can open .cgm file extensions by default.Affected if CGM file parsing modules or handlers are present in the installation
The environment is affected if either JT2Go or Teamcenter Visualization is installed with a version number below 13.1.0.1 and the CGM parsing feature is available, as processing a malicious CGM file could trigger the buffer overread.
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 to obtain the patched application. Avoid opening untrusted CGM files from unknown sources until update is applied.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27004 — 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-27004 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