CVE-2021-34320
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.2), Teamcenter Visualization (All versions < V13.2). The Jt981.dll library in affected applications lacks proper validation of user-supplied data when parsing JT files. This could result in an out of bounds read past the end of an allocated buffer. An attacker could leverage this vulnerability to leak information in the context of the current process. (ZDI-CAN-13406)
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 confidenceAn out-of-bounds read vulnerability exists in the JT981.dll library within JT2Go and Teamcenter Visualization. The library fails to properly validate user-supplied data when parsing JT files, allowing an attacker to read beyond allocated buffer boundaries and leak sensitive information from the process memory.
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.2.0< 13.2.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
- 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.
-
Verify if JT2Go or Teamcenter Visualization is installedCheck for the presence of JT2Go in Program Files or Teamcenter Visualization in the installed application directory. On Windows, review installed programs via Control Panel > Programs and Features, or use: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName, DisplayVersionAffected if Either JT2Go or Teamcenter Visualization appears in the installed programs list
-
Determine the installed version of JT2GoNavigate to the JT2Go installation directory (typically C:\Program Files\Siemens\JT2Go) and locate the version information. Right-click on JT2Go.exe, select Properties, and check the Details tab for File Version or Product Version. Alternatively, right-click the JT981.dll library and inspect its version properties.Affected if The version listed is below 13.2.0 or the version field shows nothing and the file predates the V13.2 release
-
Determine the installed version of Teamcenter VisualizationNavigate to the Teamcenter Visualization installation directory and locate the main executable or the JT981.dll library. Right-click on the executable or JT981.dll, select Properties, and check the Details tab for version information.Affected if The version shown is below 13.2.0 or version information is absent with the library appearing outdated
-
Locate and verify the JT981.dll librarySearch for JT981.dll across the system using Windows Explorer search or from PowerShell: Get-ChildItem -Path 'C:\' -Filter 'JT981.dll' -Recurse -ErrorAction SilentlyContinue. Note the full path and file version properties.Affected if The JT981.dll file is found and its version, when determinable, is prior to the V13.2 patch release
The environment is affected if either JT2Go or Teamcenter Visualization is installed with a version number lower than 13.2.0, or if the JT981.dll library is present but cannot be confirmed as V13.2 or later.
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.2.0
Upgrade JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched library. Additionally, exercise caution when opening JT files from untrusted sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34320 — 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-2021-34320 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