dbcve.org
Jt2goApplication · Siemens

CVE-2023-51439

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 an out of bounds read past the end of an allocated structure 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

An out-of-bounds read vulnerability exists in JT2Go and Teamcenter Visualization applications when parsing specially crafted CGM files. The vulnerability allows reading past the end of an allocated memory structure, which can be exploited for code execution in the context of the current process.

MitigationUpdate affected applications to the patched versions: JT2Go V14.3.0.6, Teamcenter Visualization V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6 (or later). Until patched, 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. Check if JT2Go is installed
    Locate the JT2Go installation directory and look for version information in the application executable or manifest files, typically found in the program files folder.
    Affected if JT2Go version is present and is less than 14.3.0.6
  2. Check if Teamcenter Visualization is installed
    Locate the Teamcenter Visualization installation directory and check the version information in the application executable or version file.
    Affected if Teamcenter Visualization version is present and falls within 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
  3. Verify installed version numbers
    Use the application's 'About' dialog, help menu, or run the executable with a version flag if available. Compare against the affected version ranges.
    Affected if The installed version number is lower than the patched versions (14.3.0.6 for JT2Go; 13.3.0.13, 14.1.0.12, 14.2.0.9, or 14.3.0.6 for Teamcenter Visualization)
  4. Confirm CGM file handling capability
    Check if the installed application can process or open CGM (Computer Graphics Metafile) files, which is the vulnerable file format.
    Affected if The application has the capability to parse CGM files and the user or automated processes could be persuaded to open untrusted CGM files

You are affected if you have JT2Go version below 14.3.0.6 or Teamcenter Visualization in any of the specified vulnerable version ranges, and you use these applications to open CGM 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 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

Update affected applications to the patched versions: JT2Go V14.3.0.6, Teamcenter Visualization V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6 (or later). Until patched, avoid opening untrusted CGM files.

Recommended fix High confidence

JT2Go V14.3.0.6; Teamcenter Visualization V13.3.0.13, V14.1.0.12, V14.2.0.9, or V14.3.0.6 (or later respective releases)

  1. Upgrade Jt2go to version 14.3.0.6 or later
  2. Upgrade Teamcenter Visualization V13.3 to version 13.3.0.13 or later
  3. Upgrade Teamcenter Visualization V14.1 to version 14.1.0.12 or later
  4. Upgrade Teamcenter Visualization V14.2 to version 14.2.0.9 or later
  5. Upgrade Teamcenter Visualization V14.3 to version 14.3.0.6 or later
  6. Obtain the updates from the official Siemens cert-portal or product support channels
  7. Apply the updates following standard Siemens installation procedures for your product version
Caveat Review Siemens release notes for any compatibility notes or known issues before upgrading

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