dbcve.org
Jt2goApplication · Siemens

CVE-2022-39136

HIGH · 7.8 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to 14.0.0.3 / 14.1.0.4 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.1.0.4), Teamcenter Visualization V13.2 (All versions < V13.2.0.12), Teamcenter Visualization V13.3 (All versions < V13.3.0.7), Teamcenter Visualization V13.3 (All versions >= V13.3.0.7 < V13.3.0.8), Teamcenter Visualization V14.0 (All versions < V14.0.0.3), Teamcenter Visualization V14.1 (All versions < V14.1.0.4). The affected application is vulnerable to fixed-length heap-based buffer while parsing specially crafted TIF files. An attacker could leverage this vulnerability 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

A heap-based buffer overflow vulnerability exists in the TIF file parsing functionality of JT2Go and Teamcenter Visualization applications. The vulnerability is triggered when parsing specially crafted TIF files with fixed-length buffers, allowing an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate JT2Go to version V14.1.0.4 or later, and update Teamcenter Visualization to the patched versions (V13.2.0.12, V13.3.0.8, V14.0.0.3, or V14.1.0.4 depending on the release line).

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.1.0.4
Teamcenter VisualizationApplication
Affected:<= 13.3.0.7>= 14.0, < 14.0.0.3>= 14.1, < 14.1.0.4

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. Look for executable files such as JT2Go.exe (typically in C:\Program Files\Siemens\JT2Go\) or Teamcenter Visualization binaries.
    Affected if Either product is installed
  2. Determine JT2Go version
    If JT2Go is installed, right-click JT2Go.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, run the application and check Help > About.
    Affected if Version is lower than 14.1.0.4
  3. Determine Teamcenter Visualization version
    If Teamcenter Visualization is installed, check the executable version (such as Visualization.exe or associated DLLs) via Properties > Details, or check the installation directory for version information.
    Affected if Version is 13.3.0.7 or lower, OR between 14.0.0.0 and 14.0.0.2, OR between 14.1.0.0 and 14.1.0.3
  4. Verify TIF file handling capability
    Check if the application can open or preview TIF files. Attempt to open a TIF file in the affected product, or check file association settings for .tif/.tiff extensions.
    Affected if The application can parse TIF files and the version is within the affected ranges

The environment is affected if either JT2Go version is below 14.1.0.4 or Teamcenter Visualization matches the affected version ranges AND the application is used to process TIF 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.0.0.3 / 14.1.0.4 or later
Fixed in 14.0.0.314.1.0.4
Interim mitigation

Update JT2Go to version V14.1.0.4 or later, and update Teamcenter Visualization to the patched versions (V13.2.0.12, V13.3.0.8, V14.0.0.3, or V14.1.0.4 depending on the release line).

Recommended fix High confidence

Jt2go: 14.1.0.4+ | Teamcenter Visualization: 13.2.0.12+, 13.3.0.8+, 14.0.0.3+, or 14.1.0.4+ depending on current branch

  1. 1. Identify the currently installed Jt2go or Teamcenter Visualization version
  2. 2. For Jt2go: Upgrade to version 14.1.0.4 or later
  3. 3. For Teamcenter Visualization V13.2: Upgrade to version 13.2.0.12 or later
  4. 4. For Teamcenter Visualization V13.3: Upgrade to version 13.3.0.8 or later
  5. 5. For Teamcenter Visualization V14.0: Upgrade to version 14.0.0.3 or later
  6. 6. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.4 or later
  7. 7. Obtain the updated software from the official Siemens cert-portal or Siemens PLM support channels
  8. 8. Apply the upgrade following standard Siemens installation procedures
Caveat Review Siemens release notes for version 14.1.0.4 for any compatibility or migration considerations

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-2022-39136 — 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-2022-39136 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