dbcve.org
Jt2goApplication · Siemens

CVE-2024-32636

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 14.2.0.12 / 14.3.0.10 or later.
See remediation →
81/100
Remediation priority · High
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 < V2312.0005), Teamcenter Visualization V14.2 (All versions < V14.2.0.12), Teamcenter Visualization V14.3 (All versions < V14.3.0.10), Teamcenter Visualization V2312 (All versions < V2312.0005). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process.

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

Out-of-bounds read vulnerability in JT2Go and Teamcenter Visualization applications when parsing X_T files. The parser reads past the end of an allocated memory structure, leading to memory corruption that could allow arbitrary code execution in the context of the current process.

MitigationApply vendor patches: update JT2Go and Teamcenter Visualization V2312 to V2312.0005, V14.2 to V14.2.0.12, and V14.3 to V14.3.0.10. Avoid opening untrusted X_T files until patches are applied.

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:>= 2312.0, < 2312.0005
ParasolidApplication
Affected:>= 35.1, < 35.1.256>= 36.0, < 36.0.208>= 36.1, < 36.1.173
Teamcenter VisualizationApplication
Affected:>= 14.2, < 14.2.0.12>= 14.3, < 14.3.0.10>= 2312.0, < 2312.0005

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

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

  1. Check if JT2Go is installed
    Look for JT2Go installation directory or check Windows Programs and Features for 'Siemens JT2Go' entry. Use registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode} or check C:\Program Files\Siemens\JT2Go if present.
    Affected if JT2Go is installed with version >= 2312.0 and < 2312.0005
  2. Check if Teamcenter Visualization is installed
    Look for Teamcenter Visualization installation, typically under C:\Program Files\Siemens\Teamcenter<version>\Visualization or check Windows Programs and Features for 'Siemens Teamcenter Visualization' entry.
    Affected if Teamcenter Visualization is installed with version >= 14.2.0 and < 14.2.0.12, or >= 14.3.0 and < 14.3.0.10, or >= 2312.0 and < 2312.0005
  3. Determine installed version of JT2Go
    Open JT2Go and go to Help > About, or check the version in the executable properties (right-click JT2Go.exe > Properties > Details). The version string format is like 2312.0004.
    Affected if Version starts with 2312.0 but is less than 2312.0005 (for example, 2312.0004)
  4. Determine installed version of Teamcenter Visualization
    Check the version from the installation directory or from Programs and Features. The version may be displayed as V14.2.0.11, V14.3.0.9, or V2312.0004 for affected versions.
    Affected if Version is 14.2.0.x where x < 12, or 14.3.0.x where x < 10, or 2312.0xxx where xxx < 0005
  5. Check if X_T file parser is used
    The vulnerability triggers when opening X_T files in JT2Go or Teamcenter Visualization. There is no separate configuration to disable this parser; it is a built-in feature of these applications.
    Affected if Users open or process X_T files using the affected software versions

You are affected if JT2Go version is 2312.0 to 2312.0004, or Teamcenter Visualization is version 14.2.0.0 to 14.2.0.11, 14.3.0.0 to 14.3.0.9, or 2312.0 to 2312.0004, and you open X_T files with these applications.

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.

dbcve · scoped
Upgrade available Upgrade to 14.2.0.12 / 14.3.0.10 / 35.1.256 or later
Fixed in 14.2.0.1214.3.0.1035.1.256
Interim mitigation

Apply vendor patches: update JT2Go and Teamcenter Visualization V2312 to V2312.0005, V14.2 to V14.2.0.12, and V14.3 to V14.3.0.10. Avoid opening untrusted X_T files until patches are applied.

Recommended fix High confidence

Jt2go: V2312.0005 | Teamcenter Visualization V14.2: V14.2.0.12 | Teamcenter Visualization V14.3: V14.3.0.10 | Teamcenter Visualization V2312: V2312.0005 | Parasolid: V35.1.256, V36.0.208, or V36.1.173

  1. 1. Identify the affected product and current version installed (Jt2go, Parasolid, or Teamcenter Visualization)
  2. 2. For Jt2go: upgrade to version 2312.0005 or later
  3. 3. For Teamcenter Visualization V14.2: upgrade to version 14.2.0.12 or later
  4. 4. For Teamcenter Visualization V14.3: upgrade to version 14.3.0.10 or later
  5. 5. For Teamcenter Visualization V2312: upgrade to version 2312.0005 or later
  6. 6. For Parasolid: if using version 35.1.x, upgrade to 35.1.256 or later; if using 36.0.x, upgrade to 36.0.208 or later; if using 36.1.x, upgrade to 36.1.173 or later
  7. 7. After upgrading, verify the X_T file parser handles files correctly and does not exhibit the out-of-bounds read behavior
Caveat Upgrades within the same major release typically have minimal compatibility concerns; ensure any custom templates or integrations are tested after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jt2go Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-32636 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