dbcve.org
Jt2goApplication · Siemens

CVE-2023-51744

MEDIUM · 5.5 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 →
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 < 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 null pointer dereference vulnerability while parsing specially crafted CGM 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 · moderate confidence

A null pointer dereference vulnerability exists in JT2Go and Teamcenter Visualization applications when parsing specially crafted CGM (Computer Graphics Metafile) files. Successful exploitation causes the application to crash, resulting in denial of service.

MitigationUpgrade to JT2Go V14.3.0.6 or later, and to the respective patched versions for Teamcenter Visualization (V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6).

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
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 if JT2Go is installed
    Locate the JT2Go installation directory or check system for JT2Go executable. Common paths may include Program Files/Siemens/JT2Go or similar. Check the application's About or Help section for version information.
    Affected if JT2Go version is found to be less than 14.3.0.6
  2. Identify if Teamcenter Visualization is installed
    Locate the Teamcenter Visualization installation. Check the application's About or Help menu for version information, or look for version details in the installation directory.
    Affected if Teamcenter Visualization version falls within any of these ranges: >= 13.3.0 and < 13.3.0.13, OR >= 14.1.0 and < 14.1.0.12, OR >= 14.2.0 and < 14.2.0.9, OR >= 14.3.0 and < 14.3.0.6
  3. Confirm CGM parsing capability is present
    Verify that the application can open or process CGM (Computer Graphics Metafile) files. This is typically a core feature of these visualization products. Check file association settings or try opening a CGM file if available.
    Affected if The application includes CGM file parsing functionality, which is standard for these visualization tools

You are affected if either JT2Go version is below 14.3.0.6 or Teamcenter Visualization version falls within any of the affected ranges AND the CGM parsing feature is accessible in your 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 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

Upgrade to JT2Go V14.3.0.6 or later, and to the respective patched versions for Teamcenter Visualization (V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6).

Recommended fix High confidence

Jt2go: V14.3.0.6 or later | Teamcenter Visualization V13.3: V13.3.0.13 or later | Teamcenter Visualization V14.1: V14.1.0.12 or later | Teamcenter Visualization V14.2: V14.2.0.9 or later | Teamcenter Visualization V14.3: V14.3.0.6 or later

  1. 1. Identify the currently installed product (Jt2go or Teamcenter Visualization) and its version number
  2. 2. Determine the appropriate fixed version based on the product line: Jt2go needs V14.3.0.6+, Teamcenter Visualization V13.3 needs V13.3.0.13+, V14.1 needs V14.1.0.12+, V14.2 needs V14.2.0.9+, or V14.3 needs V14.3.0.6+
  3. 3. Obtain the fixed version from Siemens support portal (cert-portal.siemens.com) or official Siemens download channels
  4. 4. Backup any critical data and configurations before upgrading
  5. 5. Install the fixed version following Siemens standard upgrade procedures
  6. 6. Verify the installation completed successfully
  7. 7. Test that the application can parse CGM files without crashing

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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