dbcve.org
Jt2goApplication · Siemens

CVE-2022-41662

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 products contain an out of bounds read vulnerability when parsing a CGM file. An attacker can 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

An out-of-bounds read vulnerability exists in the CGM file parsing functionality of JT2Go and Teamcenter Visualization products. When parsing specially crafted CGM files, the affected software reads memory beyond allocated buffers, which can be leveraged 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 patched versions (V13.2.0.12, V13.3.0.7, V14.0.0.3, or V14.1.0.4 depending on the product 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, < 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 JT2Go version
    Locate the JT2Go executable (typically in Program Files/Siemens/JT2Go or Program Files (x86)/Siemens/JT2Go), right-click the executable, select Properties, and view the File Version on the Details tab. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Siemens\JT2Go\CurrentVersion for the ProductVersion value.
    Affected if The installed version is lower than 14.1.0.4
  2. Check Teamcenter Visualization version
    Locate the Visualization executable (commonly in the Teamcenter installation directory, often under Program Files/Siemens/TeamcenterXXX/Visualization). Check the executable's Properties > Details for Product Version, or query the Windows Registry under HKLM\SOFTWARE\Siemens\Teamcenter\<version>\Visualization\InstalledVersion.
    Affected if The installed version is 13.3.0.x where x < 7, or 14.0.x where x < 3, or 14.1.x where x < 4, or any version between 13.3.0 and 13.3.0.6, or 14.0.0.0 through 14.0.0.2, or 14.1.0.0 through 14.1.0.3
  3. Determine if CGM parsing is in use
    Review recent user activity or automated workflows that involve opening CGM (Computer Graphics Metafile) files. Check for .cgm file extensions in recent document histories or temporary directories accessed by the affected applications.
    Affected if CGM files are being opened, imported, or processed by the vulnerable software versions
  4. Identify the installation path
    Use Windows Task Manager to identify running processes (JT2Go.exe or Teamcenter Visualization processes), right-click and select Open file location to confirm the installation directory and verify which product is installed.
    Affected if Either JT2Go.exe or Teamcenter Visualization binaries are present and running

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 you process CGM files with these applications.

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 patched versions (V13.2.0.12, V13.3.0.7, V14.0.0.3, or V14.1.0.4 depending on the product line).

Recommended fix High confidence

JT2Go: V14.1.0.4 | Teamcenter Visualization: V13.2.0.12, V13.3.0.7, V14.0.0.3, or V14.1.0.4 (depending on your product line)

  1. 1. Identify the installed version of JT2Go or Teamcenter Visualization by checking the application or system information
  2. 2. For JT2Go: Upgrade to version V14.1.0.4 or later
  3. 3. For Teamcenter Visualization V13.2: Upgrade to version V13.2.0.12 or later
  4. 4. For Teamcenter Visualization V13.3: Upgrade to version V13.3.0.7 or later
  5. 5. For Teamcenter Visualization V14.0: Upgrade to version V14.0.0.3 or later
  6. 6. For Teamcenter Visualization V14.1: Upgrade to version V14.1.0.4 or later
  7. 7. Verify the upgrade was successful by checking the installed version matches or exceeds the fixed version
  8. 8. Test that CGM file parsing functionality works correctly in the updated version

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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