CVE-2021-34310
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 Tiff_loader.dll library in affected applications lacks proper validation of user-supplied data when parsing TIFF files. This could result in an out of bounds write past the end of an allocated structure. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13351)
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 confidenceThe Tiff_loader.dll library in JT2Go and Teamcenter Visualization lacks proper validation of user-supplied data when parsing TIFF files, leading to an out-of-bounds write past the end of an allocated structure. This memory corruption vulnerability can be triggered by a malicious TIFF file and allows remote 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.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.
-
Identify installed Siemens productCheck for presence of JT2Go or Teamcenter Visualization installation directories. Common paths: %ProgramFiles%\Siemens\JT2Go or %ProgramFiles%\Siemens\Teamcenter Visualization. Use Get-ItemProperty on registry key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for installed applications.Affected if Neither JT2Go nor Teamcenter Visualization is installed, then not affected.
-
Determine installed product versionLocate the version information in the product's main executable or DLL. For JT2Go, check jt2go.exe properties. For Teamcenter Visualization, check the installation directory for version metadata. Use (Get-Item 'C:\Program Files\Siemens\JT2Go\jt2go.exe').VersionInfo or similar path.Affected if Version is less than 13.2.0, indicating affected.
-
Locate Tiff_loader.dllSearch for Tiff_loader.dll in the product installation directory, typically under the bin or main application folder. Use Get-ChildItem -Recurse -Filter Tiff_loader.dll within the Siemens product folder.Affected if Tiff_loader.dll exists in the product directory, confirming the vulnerable component is present.
-
Check Tiff_loader.dll versionRight-click Tiff_loader.dll, select Properties, then Details to view File Version. Alternatively, use (Get-Item 'path\to\Tiff_loader.dll').VersionInfo to retrieve version details.Affected if DLL version is below the V13.2 baseline, confirming vulnerability.
User is affected if either JT2Go or Teamcenter Visualization is installed with a version earlier than 13.2.0 and the Tiff_loader.dll is present, meaning the software can be triggered to parse a malicious TIFF file leading to out-of-bounds memory write.
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, which contains the patched Tiff_loader.dll library with proper input validation.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34310 — 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-34310 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