Jt2goApplication · Siemens

CVE-2021-34302

MEDIUM · 5.5 CVSS v3.1 Published 2021-07-13
Fix available
A fix is available. Upgrade to 13.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
A 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 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-13197)

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 confidence

The BMP_Loader.dll library in JT2Go and Teamcenter Visualization lacks proper bounds checking when parsing BMP files, allowing an out-of-bounds read past the end of an allocated buffer. An attacker can exploit this by tricking a user into opening a specially crafted BMP file, leaking sensitive information from process memory.

MitigationUpgrade JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched BMP_Loader.dll library.

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
Jt2goApplication
Affected:< 13.2.0
Teamcenter VisualizationApplication
Affected:< 13.2.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify which affected product is installed
    Check for JT2Go or Teamcenter Visualization installation directories. Common paths: JT2Go typically in Program Files/Siemens/JT2Go, Teamcenter Visualization in Program Files/Siemens/TcVis or similar.
    Affected if Either JT2Go or Teamcenter Visualization is installed on the system
  2. Determine installed version of JT2Go
    Open JT2Go and navigate to Help > About, or check the file version of JT2Go.exe in the installation directory (right-click > Properties > Details).
    Affected if The version displayed is below 13.2.0
  3. Determine installed version of Teamcenter Visualization
    Open Teamcenter Visualization and check About information, or check the file version of the main executable in the installation directory.
    Affected if The version displayed is below 13.2.0
  4. Locate BMP_Loader.dll in the installation
    Search for BMP_Loader.dll within the product installation directory. Use File Explorer search or run: dir /s "BMP_Loader.dll" at the installation root.
    Affected if BMP_Loader.dll exists in the product folder and version check above shows vulnerable version
  5. Confirm the DLL file version if available
    Right-click BMP_Loader.dll > Properties > Details to view File Version. Compare against known fixed version if available.
    Affected if File version is present and below the patched version in 13.2.0

The environment is affected if either JT2Go or Teamcenter Visualization is installed with a version lower than 13.2.0, as this indicates the vulnerable BMP_Loader.dll library is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 13.2.0 or later
Fixed in 13.2.0
Interim mitigation

Upgrade JT2Go and Teamcenter Visualization to version V13.2 or later to obtain the patched BMP_Loader.dll library.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34302 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34302 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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