dbcve.org
Jt2goApplication · Siemens

CVE-2024-32637

MEDIUM · 5.5 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 →
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 < 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 a null pointer dereference vulnerability while parsing specially crafted X_T files. An attacker could leverage this vulnerability to crash the application causing denial of service condition.

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

A null pointer dereference vulnerability exists in JT2Go and Teamcenter Visualization products when parsing specially crafted X_T files. The vulnerability can be triggered by a user opening a malicious X_T file, causing the application to crash and resulting in a denial of service condition.

MitigationUpdate affected products to the patched versions: JT2Go and Teamcenter Visualization V2312 to V2312.0005, Teamcenter Visualization V14.2 to V14.2.0.12, and Teamcenter Visualization V14.3 to V14.3.0.10.

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.0, < 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Identify installed JT2Go version
    Locate the JT2Go installation directory and check the product version information (typically in the application properties, about dialog, or version file within the program folder)
    Affected if The installed version is >= 2312.0 and < 2312.0005
  2. Identify installed Teamcenter Visualization version
    Check the Teamcenter Visualization product version through the application, installer properties, or version metadata in the installation directory
    Affected if The installed version falls within any of these ranges: >= 14.2 and < 14.2.0.12, OR >= 14.3 and < 14.3.0.10, OR >= 2312.0 and < 2312.0005
  3. Identify installed Parasolid version
    Check the Parasolid version if installed as a standalone component or embedded library (check version file, or query through the host application that uses Parasolid)
    Affected if The installed version falls within any of these ranges: >= 35.0 and < 35.1.256, OR >= 36.0 and < 36.0.208, OR >= 36.1 and < 36.1.173
  4. Confirm X_T file parsing capability is present
    Verify that the product has the ability to import or open X_T files (this is a built-in feature; if the product supports X_T format, the vulnerable parsing code is present)
    Affected if The product can parse X_T files and the version check in steps 1-3 shows an affected version

You are affected if you have any of the affected products (JT2Go, Teamcenter Visualization, or Parasolid) installed with a version matching the affected ranges AND the product includes X_T file parsing functionality.

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

Update affected products to the patched versions: JT2Go and Teamcenter Visualization V2312 to V2312.0005, Teamcenter Visualization V14.2 to V14.2.0.12, and Teamcenter Visualization V14.3 to V14.3.0.10.

Recommended fix High confidence

JT2Go: V2312.0005 | Teamcenter Visualization: V14.2.0.12, V14.3.0.10, or V2312.0005 (depending on branch) | Parasolid: V35.1.256, V36.0.208, or V36.1.173 (depending on branch)

  1. 1. Identify the specific affected product(s) in your environment: JT2Go, Parasolid, and/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 V35.x: Upgrade to version 35.1.256 or later
  7. 7. For Parasolid V36.0.x: Upgrade to version 36.0.208 or later
  8. 8. For Parasolid V36.1.x: Upgrade to version 36.1.173 or later
Caveat Standard upgrade considerations apply - review release notes for your specific version for any functionality changes

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32637 — 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-32637 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