dbcve.org
Jt2goApplication · Siemens

CVE-2024-26275

HIGH · 7.8 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 →
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.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 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, Parasolid (V35.1, V36.0, V36.1), and Teamcenter Visualization (V14.2, V14.3, V2312) when parsing specially crafted X_T files. The vulnerability allows reading past the end of an allocated structure, potentially enabling code execution in the context of the current process.

MitigationUpdate all affected products to their fixed versions: JT2Go V2312.0004, Parasolid V35.1.254/V36.0.207/V36.1.147, and Teamcenter Visualization V14.2.0.12/V14.3.0.9/V2312.0004 or later.

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.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
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 Siemens JT2Go is installed
    Locate the JT2Go installation directory and identify the version file or executable version information
    Affected if JT2Go version is >= 2312.0 and < 2312.0004
  2. Check if Siemens Parasolid is installed
    Locate the Parasolid installation and identify the version information, typically found in the product manifest or version file
    Affected if Parasolid version is >= 35.1 and < 35.1.254, OR >= 36.0 and < 36.0.207, OR >= 36.1 and < 36.1.147
  3. Check if Siemens Teamcenter Visualization is installed
    Locate the Teamcenter Visualization installation and identify the version information, typically found in the product manifest or version file
    Affected if Teamcenter Visualization version is >= 14.2 and < 14.2.0.12, OR >= 14.3 and < 14.3.0.9, OR >= 2312.0 and < 2312.0004
  4. Verify X_T file parsing capability
    Determine if the X_T file parser module is present and enabled in the installed product (this is typically a core parsing component)
    Affected if The X_T parser module is loaded and the product version falls within the affected ranges above

If any of these products are installed and their installed versions fall within the affected ranges listed, the environment is vulnerable to CVE-2024-26275 when parsing specially crafted X_T files.

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 all affected products to their fixed versions: JT2Go V2312.0004, Parasolid V35.1.254/V36.0.207/V36.1.147, and Teamcenter Visualization V14.2.0.12/V14.3.0.9/V2312.0004 or later.

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. 1. Identify which Siemens product(s) are in use: Jt2go, Parasolid, or Teamcenter Visualization.
  2. 2. For Jt2go: upgrade to version 2312.0004 or later.
  3. 3. For Parasolid V35.1: upgrade to version 35.1.254 or later.
  4. 4. For Parasolid V36.0: upgrade to version 36.0.207 or later.
  5. 5. For Parasolid V36.1: upgrade to version 36.1.147 or later.
  6. 6. For Teamcenter Visualization V14.2: upgrade to version 14.2.0.12 or later.
  7. 7. For Teamcenter Visualization V14.3: upgrade to version 14.3.0.9 or later.
  8. 8. For Teamcenter Visualization V2312: upgrade to version 2312.0004 or later.
Caveat Review release notes for any functional changes; minor version updates typically preserve compatibility

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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