CVE-2021-34306
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 BMP_Loader.dll library in affected applications lacks proper validation of user-supplied data when parsing BMP files. This could result in a memory corruption condition. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13342)
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 BMP_Loader.dll library in JT2Go and Teamcenter Visualization fails to validate user-supplied data during BMP file parsing, leading to memory corruption. An attacker can exploit this by tricking a user into opening a specially crafted BMP file, potentially achieving 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 visualization productsCheck Program Files or Program Files (x86) for Siemens JT2Go or Teamcenter Visualization folders. Also check Windows Registry under HKLM\SOFTWARE\Siemens for these products.Affected if Either JT2Go or Teamcenter Visualization is found installed on the system
-
Check installed product versionLocate the main executable (JT2Go.exe or Teamcenter Visualization executable) in the installation folder, right-click and select Properties, then check the Details tab for the File Version. Alternatively, check the version in Add/Remove Programs.Affected if The installed version is lower than 13.2.0
-
Locate BMP_Loader.dllSearch for BMP_Loader.dll within the product installation directory (typically in the bin or main application folder). The DLL is the vulnerable component.Affected if BMP_Loader.dll exists in the JT2Go or Teamcenter Visualization installation directory
-
Check BMP_Loader.dll versionRight-click BMP_Loader.dll, select Properties, and check the File Version field in the Details tab.Affected if The DLL version is earlier than the version bundled with V13.2.0 (confirm by comparing against the patched DLL in V13.2.0)
The environment is affected if JT2Go or Teamcenter Visualization is installed with a version lower than 13.2.0 and the BMP_Loader.dll library is present, meaning the application can be triggered to parse BMP files.
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
Update JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched BMP_Loader.dll library. Avoid opening untrusted BMP files from unknown sources until the update is applied.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34306 — 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-34306 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