dbcve.org
Jt2goApplication · Siemens

CVE-2023-51745

HIGH · 7.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 13.3.0.13 / 14.1.0.12 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 < V14.3.0.6), Teamcenter Visualization V13.3 (All versions < V13.3.0.13), Teamcenter Visualization V14.1 (All versions < V14.1.0.12), Teamcenter Visualization V14.2 (All versions < V14.2.0.9), Teamcenter Visualization V14.3 (All versions < V14.3.0.6). The affected applications contain a stack overflow vulnerability while parsing specially crafted CGM 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 JT2Go and Teamcenter Visualization when parsing specially crafted CGM files allows arbitrary code execution in the context of the current process.

MitigationApply vendor patches to update to version V14.3.0.6 (JT2Go), V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6 respectively. Avoid opening untrusted CGM files.

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:< 14.3.0.6
Teamcenter VisualizationApplication
Affected:>= 13.3.0, < 13.3.0.13>= 14.1, < 14.1.0.12>= 14.2, < 14.2.0.9>= 14.3, < 14.3.0.6

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. Verify if JT2Go or Teamcenter Visualization is installed
    Check for the presence of JT2Go.exe or Teamcenter Visualization binaries in program directories, or look for the application in installed programs list
    Affected if Either JT2Go or Teamcenter Visualization is present on the system
  2. Determine installed version of JT2Go
    Right-click JT2Go.exe, select Properties, and check the File Version field under the Details tab. Alternatively, run 'JT2Go.exe -version' if supported
    Affected if Version is lower than 14.3.0.6
  3. Determine installed version of Teamcenter Visualization
    Check the version of the Teamcenter Visualization binaries (typically under Siemens\Teamcenter\Visualization or Teamcenter\TCVIS\bin directories) via Properties Details or using the product's About dialog
    Affected if Version falls within any of these ranges: >=13.3.0 and <13.3.0.13, or >=14.1 and <14.1.0.12, or >=14.2 and <14.2.0.9, or >=14.3 and <14.3.0.6
  4. Check if CGM import feature is enabled or accessible
    Launch the application and verify whether CGM file import capability is available. Check application settings or file type associations for .cgm files
    Affected if CGM parsing functionality is present and accessible to the user

The environment is affected if either JT2Go (any version below 14.3.0.6) or Teamcenter Visualization (any version in the vulnerable ranges) is installed with CGM file parsing capability accessible.

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 13.3.0.13 / 14.1.0.12 / 14.2.0.9 or later
Fixed in 13.3.0.1314.1.0.1214.2.0.9
Interim mitigation

Apply vendor patches to update to version V14.3.0.6 (JT2Go), V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6 respectively. Avoid opening untrusted CGM files.

Recommended fix High confidence

Jt2Go: 14.3.0.6+ | Teamcenter Visualization V13.3: 13.3.0.13+ | Teamcenter Visualization V14.1: 14.1.0.12+ | Teamcenter Visualization V14.2: 14.2.0.9+ | Teamcenter Visualization V14.3: 14.3.0.6+

  1. 1. Identify the installed version of Jt2Go or Teamcenter Visualization using the application's 'About' or version information.
  2. 2. For Jt2Go: If the version is below 14.3.0.6, download and install version 14.3.0.6 or later from the official Siemens support portal.
  3. 3. For Teamcenter Visualization V13.3: If the version is below 13.3.0.13, upgrade to version 13.3.0.13 or later.
  4. 4. For Teamcenter Visualization V14.1: If the version is below 14.1.0.12, upgrade to version 14.1.0.12 or later.
  5. 5. For Teamcenter Visualization V14.2: If the version is below 14.2.0.9, upgrade to version 14.2.0.9 or later.
  6. 6. For Teamcenter Visualization V14.3: If the version is below 14.3.0.6, upgrade to version 14.3.0.6 or later.
  7. 7. After upgrading, verify the new version is correctly installed.
  8. 8. As a general precaution, avoid opening untrusted CGM files until the upgrade is applied.

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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