dbcve.org
Jt2goApplication · Siemens

CVE-2024-34085

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 14.1.0.13 / 14.2.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.0001), Teamcenter Visualization V14.1 (All versions < V14.1.0.13), Teamcenter Visualization V14.2 (All versions < V14.2.0.10), Teamcenter Visualization V14.3 (All versions < V14.3.0.7), Teamcenter Visualization V2312 (All versions < V2312.0001). The affected applications contain a stack overflow vulnerability while parsing specially crafted XML 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

Stack overflow vulnerability in XML file parsing in JT2Go and Teamcenter Visualization products. Specially crafted XML files can trigger the overflow, potentially allowing arbitrary code execution in the context of the current process.

MitigationUpdate JT2Go to V2312.0001 or later, and Teamcenter Visualization to the version corresponding to your release line (V14.1.0.13, V14.2.0.10, V14.3.0.7, or V2312.0001).

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.0001
Teamcenter VisualizationApplication
Affected:>= 14.1, < 14.1.0.13>= 14.2, < 14.2.0.10>= 14.3, < 14.3.0.7>= 2312.0, < 2312.0001

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. Identify installed product
    Check if Siemens JT2Go or Teamcenter Visualization is installed on the system. Look for installation directories or check program lists.
    Affected if Either JT2Go or Teamcenter Visualization is installed
  2. Check JT2Go version
    Locate the JT2Go installation and check the version. This is typically found in the application executable properties or installer information.
    Affected if JT2Go version is lower than 2312.0001
  3. Check Teamcenter Visualization version
    Locate the Teamcenter Visualization installation and check the version. This is typically found in the application executable properties or installer information.
    Affected if Teamcenter Visualization version falls in any of these ranges: >=14.1 and <14.1.0.13, >=14.2 and <14.2.0.10, >=14.3 and <14.3.0.7, or >=2312.0 and <2312.0001
  4. Verify XML file handling capability
    Confirm the installed software can process XML files, which is a standard capability for JT2Go and Teamcenter Visualization when handling CAD data.
    Affected if The software can open or parse XML-based files (which is a core function of these products)

If either JT2Go version is below 2312.0001 or Teamcenter Visualization version is in any of the affected ranges listed, the system is vulnerable when processing XML 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.1.0.13 / 14.2.0.10 / 14.3.0.7 or later
Fixed in 14.1.0.1314.2.0.1014.3.0.7
Interim mitigation

Update JT2Go to V2312.0001 or later, and Teamcenter Visualization to the version corresponding to your release line (V14.1.0.13, V14.2.0.10, V14.3.0.7, or V2312.0001).

Recommended fix High confidence

JT2Go: V2312.0001 | Teamcenter Visualization: V14.1.0.13, V14.2.0.10, V14.3.0.7, or V2312.0001 (depending on current branch)

  1. 1. Identify the currently installed version of JT2Go or Teamcenter Visualization
  2. 2. For JT2Go users: Upgrade to version V2312.0001 or later
  3. 3. For Teamcenter Visualization V14.1 users: Upgrade to version V14.1.0.13 or later
  4. 4. For Teamcenter Visualization V14.2 users: Upgrade to version V14.2.0.10 or later
  5. 5. For Teamcenter Visualization V14.3 users: Upgrade to version V14.3.0.7 or later
  6. 6. For Teamcenter Visualization V2312 users: Upgrade to version V2312.0001 or later
  7. 7. Obtain the updates from the official Siemens support portal or through your standard software distribution channel
  8. 8. Verify the installation of the patched version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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