dbcve.org
Jt2goApplication · Siemens

CVE-2022-41663

HIGH · 7.8 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to 13.3.0.7 / 14.0.0.3 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 V14.0 (All versions < V14.0.0.3), Teamcenter Visualization V14.1 (All versions < V14.1.0.4). The affected applications contain a use-after-free vulnerability that could be triggered while parsing specially crafted CGM 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

Use-after-free vulnerability in JT2Go and Teamcenter Visualization applications when parsing specially crafted CGM (Computer Graphics Metafile) files. An attacker can exploit this to execute arbitrary code in the context of the current process.

MitigationUpdate JT2Go to version V14.1.0.4 or later, and Teamcenter Visualization to the appropriate patched version (V13.2.0.12, V13.3.0.7, V14.0.0.3, or V14.1.0.4 depending on the product line). Avoid opening untrusted CGM files until patched.

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, < 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. Check if JT2Go is installed
    Look for JT2Go installation directory or check program files. Common paths: C:\Program Files\Siemens\JT2Go or %LOCALAPPDATA%\Siemens\JT2Go. On Linux, check /opt/siemens/jt2go or similar.
    Affected if JT2Go is installed and version is below 14.1.0.4
  2. Check if Teamcenter Visualization is installed
    Look for Teamcenter Visualization installation. Common paths: C:\Program Files\Siemens\Teamcenter Visualization or C:\Program Files\Siemens\TCVis. Check for executables like TCVis.exe or Visualization.exe in installation directories.
    Affected if Teamcenter Visualization is installed and version is 13.3.0.x (below 13.3.0.7), 14.0.x (below 14.0.0.3), or 14.1.x (below 14.1.0.4)
  3. Determine installed version of JT2Go
    Right-click on JT2Go.exe, select Properties, go to Details tab, check Product Version. Or run: "C:\Program Files\Siemens\JT2Go\JT2Go.exe" /version if supported.
    Affected if Version displayed is less than 14.1.0.4
  4. Determine installed version of Teamcenter Visualization
    Right-click on the main executable (often TCVis.exe or Visualization.exe), select Properties, go to Details tab, check Product Version. Check version from the application About dialog if accessible.
    Affected if Version starts with 13.3.0 and is below 13.3.0.7, starts with 14.0.0 and is below 14.0.0.3, or starts with 14.1.0 and is below 14.1.0.4
  5. Identify if CGM file parsing capability exists
    These are visualization applications designed to read CGM files by default. Check if the application can open .cgm files or has CGM import functionality. No configuration change is needed to be vulnerable - the flaw exists in the parsing routine itself.
    Affected if The application can import or open CGM files (default functionality for both products)

You are affected if either JT2Go version is below 14.1.0.4 or Teamcenter Visualization version is 13.3.0.x before 13.3.0.7, 14.0.x before 14.0.0.3, or 14.1.x before 14.1.0.4, and the application can process CGM files (default behavior).

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.7 / 14.0.0.3 / 14.1.0.4 or later
Fixed in 13.3.0.714.0.0.314.1.0.4
Interim mitigation

Update JT2Go to version V14.1.0.4 or later, and Teamcenter Visualization to the appropriate patched version (V13.2.0.12, V13.3.0.7, V14.0.0.3, or V14.1.0.4 depending on the product line). Avoid opening untrusted CGM files until patched.

Recommended fix High confidence

JT2Go: V14.1.0.4+ | Teamcenter Visualization: V13.2.0.12+, V13.3.0.7+, V14.0.0.3+, V14.1.0.4+ (depending on current branch)

  1. 1. Identify the specific product (JT2Go or Teamcenter Visualization) and current version installed in your environment
  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.7 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. Verify the upgrade was successful by checking the application version
  8. 8. Re-test any workflows that involve parsing CGM files to ensure functionality is maintained

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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