dbcve.org
Jt2goApplication · Siemens

CVE-2022-41283

HIGH · 7.8 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to 13.2.0.12 / 13.3.0.8 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.6), Teamcenter Visualization V13.2 (All versions < V13.2.0.12), Teamcenter Visualization V13.3 (All versions < V13.3.0.8), Teamcenter Visualization V14.0 (All versions < V14.0.0.4), Teamcenter Visualization V14.1 (All versions < V14.1.0.6). The CGM_NIST_Loader.dll contains an out of bounds write 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

Out of bounds write vulnerability in CGM_NIST_Loader.dll when parsing CGM files allows remote code execution in the context of the current process. The vulnerability affects multiple Teamcenter Visualization products and JT2Go across several version branches.

MitigationApply vendor patches by updating JT2Go to V14.1.0.6 or later, Teamcenter Visualization V13.2 to V13.2.0.12, V13.3 to V13.3.0.8, V14.0 to V14.0.0.4, and V14.1 to V14.1.0.6 or later.

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:all versions
Teamcenter VisualizationApplication
Affected:>= 13.2.0, < 13.2.0.12>= 13.3.0, < 13.3.0.8>= 14.0, < 14.0.0.4>= 14.1, < 14.1.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
    Look for JT2Go installation directory (commonly at Program Files/Siemens/JT2Go) or the JT2Go.exe executable on the system
    Affected if JT2Go is found on the system (all versions are affected)
  2. Check if Teamcenter Visualization is installed
    Look for Teamcenter Visualization installation directories or associated binaries such as VisViewer, Teamcenter Visualization, or TcVis
    Affected if Teamcenter Visualization is found on the system
  3. Locate the vulnerable CGM_NIST_Loader.dll
    Search for CGM_NIST_Loader.dll within the product installation directories. Common paths include the bin or program directory under the JT2Go or Teamcenter Visualization installation folder
    Affected if CGM_NIST_Loader.dll is present in the installation directory
  4. Determine the installed product version
    Right-click on JT2Go.exe or the Teamcenter Visualization executable, select Properties, and view the File Version in the Details tab. Alternatively, check version information in the installation directory or product-specific version file
    Affected if The installed version falls within any of these ranges: >= 13.2.0 and < 13.2.0.12; >= 13.3.0 and < 13.3.0.8; >= 14.0 and < 14.0.0.4; >= 14.1 and < 14.1.0.6. For JT2Go, all versions are affected.

You are affected if JT2Go or Teamcenter Visualization is installed with a version that falls below the fixed releases (13.2.0.12, 13.3.0.8, 14.0.0.4, or 14.1.0.6), or if using JT2Go at any version.

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.2.0.12 / 13.3.0.8 / 14.0.0.4 or later
Fixed in 13.2.0.1213.3.0.814.0.0.4
Interim mitigation

Apply vendor patches by updating JT2Go to V14.1.0.6 or later, Teamcenter Visualization V13.2 to V13.2.0.12, V13.3 to V13.3.0.8, V14.0 to V14.0.0.4, and V14.1 to V14.1.0.6 or later.

Recommended fix High confidence

JT2Go: V14.1.0.6 | Teamcenter Visualization V13.2: V13.2.0.12 | Teamcenter Visualization V13.3: V13.3.0.8 | Teamcenter Visualization V14.0: V14.0.0.4 | Teamcenter Visualization V14.1: V14.1.0.6

  1. Identify the installed product (JT2Go or Teamcenter Visualization) and current version
  2. For JT2Go: Download and install version 14.1.0.6 or later from the Siemens support portal
  3. For Teamcenter Visualization V13.2: Upgrade to version 13.2.0.12 or later
  4. For Teamcenter Visualization V13.3: Upgrade to version 13.3.0.8 or later
  5. For Teamcenter Visualization V14.0: Upgrade to version 14.0.0.4 or later
  6. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.6 or later
  7. Verify the installation by checking the product's About/Help section for the correct version number

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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