dbcve.org
Jt2goApplication · Siemens

CVE-2024-26276

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 14.2.0.12 / 14.3.0.9 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.0004), Parasolid V35.1 (All versions < V35.1.254), Parasolid V36.0 (All versions < V36.0.207), Parasolid V36.1 (All versions < V36.1.147), Teamcenter Visualization V14.2 (All versions < V14.2.0.12), Teamcenter Visualization V14.3 (All versions < V14.3.0.9), Teamcenter Visualization V2312 (All versions < V2312.0004). The affected application contains a stack exhaustion vulnerability while parsing a specially crafted X_T file. This could allow an attacker to cause 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

This is a stack exhaustion vulnerability in JT2Go, Parasolid, and Teamcenter Visualization applications when parsing specially crafted X_T CAD files. The vulnerability allows attackers to cause a denial of service by triggering excessive stack consumption during the parsing process, likely due to recursive or deeply nested structures in the malformed X_T file format.

MitigationUpdate affected software to the specified patched versions (JT2Go/Teamcenter Visualization V2312.0004, Parasolid V35.1.254/V36.0.207/V36.1.147) and exercise caution when opening X_T files from untrusted sources.

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.0004
ParasolidApplication
Affected:>= 35.1, < 35.1.254>= 36.0, < 36.0.207>= 36.1, < 36.1.147
Teamcenter VisualizationApplication
Affected:>= 14.2, < 14.2.0.12>= 14.3, < 14.3.0.9>= 2312.0, < 2312.0004

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 Siemens CAD application
    Check for JT2Go, Parasolid, or Teamcenter Visualization in the system program list (Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell for each product name in HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\)
    Affected if Any of these three Siemens products are installed on the system
  2. Determine JT2Go version
    Open JT2Go, navigate to Help > About JT2Go, or locate the executable and use 'Get-ItemProperty' to read the FileVersion from the properties, then compare against version 2312.0004
    Affected if The installed version is lower than 2312.0004
  3. Determine Parasolid version
    Check the Parasolid version through the host application (if bundled) or look for pxkernel.dll in the installation directory and check its version properties; compare against the affected ranges: 35.1.x before 35.1.254, 36.0.x before 36.0.207, or 36.1.x before 36.1.147
    Affected if The installed Parasolid version falls within any of the three vulnerable ranges
  4. Determine Teamcenter Visualization version
    Open Teamcenter Visualization application and check Help > About, or locate the visualization executable and check its file version properties; compare against: < 14.2.0.12 (for 14.2.x), < 14.3.0.9 (for 14.3.x), or < 2312.0004 (for 2312.x)
    Affected if The installed version is within any of the three vulnerable ranges
  5. Verify X_T file parsing capability
    Check if the application has X_T file import/enabled functionality (look for X_T, Parasolid translator, or ACIS-related modules in the application configuration or plugins directory)
    Affected if X_T file parsing is available and the application version is vulnerable according to the checks above

A user is affected if they have any of the three products installed with a version matching the vulnerable ranges AND the X_T file parsing feature is present in their environment.

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.9 / 35.1.254 or later
Fixed in 14.2.0.1214.3.0.935.1.254
Interim mitigation

Update affected software to the specified patched versions (JT2Go/Teamcenter Visualization V2312.0004, Parasolid V35.1.254/V36.0.207/V36.1.147) and exercise caution when opening X_T files from untrusted sources.

Recommended fix High confidence

JT2Go: V2312.0004 | Parasolid V35.1: V35.1.254 | Parasolid V36.0: V36.0.207 | Parasolid V36.1: V36.1.147 | Teamcenter Visualization V14.2: V14.2.0.12 | Teamcenter Visualization V14.3: V14.3.0.9 | Teamcenter Visualization V2312: V2312.0004

  1. Identify the exact product and version currently installed (JT2Go, Parasolid, or Teamcenter Visualization)
  2. For JT2Go: upgrade to version 2312.0004 or later
  3. For Parasolid V35.1: upgrade to version 35.1.254 or later
  4. For Parasolid V36.0: upgrade to version 36.0.207 or later
  5. For Parasolid V36.1: upgrade to version 36.1.147 or later
  6. For Teamcenter Visualization V14.2: upgrade to version 14.2.0.12 or later
  7. For Teamcenter Visualization V14.3: upgrade to version 14.3.0.9 or later
  8. For Teamcenter Visualization V2312: upgrade to version 2312.0004 or later

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-26276 — 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-26276 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