dbcve.org
Jt2goApplication · Siemens

CVE-2023-38682

HIGH · 7.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 14.1.0.10 / 14.2.0.5 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.2.0.5), Teamcenter Visualization V13.2 (All versions < V13.2.0.14), Teamcenter Visualization V14.1 (All versions < V14.1.0.10), Teamcenter Visualization V14.2 (All versions < V14.2.0.5). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted TIFF 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 TIFF file parsing in JT2Go and Teamcenter Visualization applications. Specially crafted TIFF files can trigger a read past the end of an allocated structure, potentially allowing code execution in the context of the current process.

MitigationUpdate to patched versions: JT2Go V14.2.0.5, Teamcenter Visualization V13.2.0.14, V14.1.0.10, or V14.2.0.5. Until patched, avoid opening untrusted TIFF 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.2.0.5
Teamcenter VisualizationApplication
Affected:>= 14.1, < 14.1.0.10>= 14.2, < 14.2.0.5

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 JT2Go version
    Open JT2Go, go to Help > About, or check the application's version property in the program files directory
    Affected if Version is lower than 14.2.0.5
  2. Identify installed Teamcenter Visualization version
    Check the application version through the product's About dialog or by examining the executable file properties
    Affected if Version is 14.1.x below 14.1.0.10, or 14.2.x below 14.2.0.5
  3. Confirm TIFF file handling is accessible
    Verify the application can open or import TIFF image files - this is the vulnerable code path
    Affected if The application has TIFF parsing functionality enabled and usable

A user is affected if they have JT2Go below 14.2.0.5 or Teamcenter Visualization in versions 14.1.0.0-14.1.0.9 or 14.2.0.0-14.2.0.4, and the application can process TIFF 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.10 / 14.2.0.5 or later
Fixed in 14.1.0.1014.2.0.5
Interim mitigation

Update to patched versions: JT2Go V14.2.0.5, Teamcenter Visualization V13.2.0.14, V14.1.0.10, or V14.2.0.5. Until patched, avoid opening untrusted TIFF files.

Recommended fix High confidence

JT2Go: V14.2.0.5 | Teamcenter Visualization V13.2: V13.2.0.14 | Teamcenter Visualization V14.1: V14.1.0.10 | Teamcenter Visualization V14.2: V14.2.0.5

  1. 1. Identify the installed product (JT2Go, Teamcenter Visualization V13.2, V14.1, or V14.2)
  2. 2. Determine the current installed version number
  3. 3. For JT2Go: Upgrade to version 14.2.0.5 or later
  4. 4. For Teamcenter Visualization V13.2: Upgrade to version 13.2.0.14 or later
  5. 5. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.10 or later
  6. 6. For Teamcenter Visualization V14.2: Upgrade to version 14.2.0.5 or later
  7. 7. Obtain the update from official Siemens channels (Siemens PLM Portal or standard update distribution)
  8. 8. Verify the vulnerability is resolved by confirming the installed version matches or exceeds the fixed version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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