CVE-2021-34324
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 prior to performing further free operations on an object when parsing JT files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13420)
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 confidenceA use-after-free or similar memory corruption vulnerability exists in Jt981.dll within JT2Go and Teamcenter Visualization. The library fails to validate user-supplied data from JT files before performing free operations on objects, allowing an attacker to execute arbitrary code by delivering a specially crafted malicious JT 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.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
- High
- Availability
- High
CVSS:3.1/AV:L/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 JT2Go installation and versionOpen Windows Settings > Apps > Apps & features, or use ' Programs and Features' control panel. Look for 'Siemens JT2Go' in the installed programs list and note the version number shown.Affected if The installed version is shown as less than 13.2.0 (for example, 13.1.x, 13.0.x, or earlier)
-
Check Teamcenter Visualization installation and versionOpen Windows Settings > Apps > Apps & features, or use 'Programs and Features' control panel. Look for 'Siemens Teamcenter Visualization' or 'Teamcenter Visualization' in the installed programs list and note the version number shown.Affected if The installed version is shown as less than 13.2.0 (for example, 13.1.x, 13.0.x, or earlier)
-
Locate and check Jt981.dll versionSearch for the file Jt981.dll on the system using File Explorer search or the command 'dir /s Jt981.dll' from the root drive. Right-click the DLL file, select Properties, and view the File Version information on the Details tab.Affected if Jt981.dll exists on the system and its file version is below 13.2.0, or the product version it belongs to is below 13.2.0
-
Compare versions against affected rangeIf you identified either product installed, compare its exact version number to the affected range: any version less than 13.2.0 is vulnerable.Affected if Either JT2Go or Teamcenter Visualization is installed with a version number less than 13.2.0
You are affected if Siemens JT2Go or Teamcenter Visualization is installed with any version lower than 13.2.0, as the vulnerable Jt981.dll library ships with these product versions.
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 13.2 or later. Until patched, do not open untrusted or unknown JT files.
- Consultation1.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34324 — 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-34324 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