dbcve.org
Jt2goApplication · Siemens

CVE-2022-41281

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 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

The CGM_NIST_Loader.dll in JT2Go and Teamcenter Visualization products has an out-of-bounds read vulnerability when parsing CGM files. This memory corruption issue can be exploited to execute arbitrary code in the context of the current process, making it a code execution vulnerability.

MitigationUpgrade JT2Go to version V14.1.0.6 or later, and Teamcenter Visualization to the corresponding fixed versions (V13.2.0.12, V13.3.0.8, V14.0.0.4, or V14.1.0.6 depending on the product line). Until patched, avoid opening untrusted CGM 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: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, typically under C:\Program Files\Siemens\JT2Go or C:\Program Files (x86)\Siemens\JT2Go. Also check Add/Remove Programs for JT2Go entry.
    Affected if JT2Go is present on the system with any version (all versions are affected).
  2. Check if Teamcenter Visualization is installed
    Look for Teamcenter Visualization installation directory, typically under C:\Program Files\Siemens\Teamcenter<version>\Visualization or check Add/Remove Programs.
    Affected if Teamcenter Visualization is present with version matching: >=13.2.0 <13.2.0.12, >=13.3.0 <13.3.0.8, >=14.0 <14.0.0.4, or >=14.1 <14.1.0.6.
  3. Identify installed version of affected product
    Check the product's About or Help menu, or look at the version info of the executable (JT2Go.exe or Visualization.exe) via right-click Properties. Compare against affected version ranges.
    Affected if Version falls within any of the vulnerable ranges listed above.
  4. Verify CGM_NIST_Loader.dll exists
    Search for CGM_NIST_Loader.dll in the product installation directory, typically in a bin or lib subfolder.
    Affected if The DLL exists and the product version is in the affected range - the vulnerability is present.
  5. Confirm CGM file handling capability
    Attempt to open a CGM file or check if the CGM import/loader module is available in the product. The vulnerability triggers when parsing CGM files.
    Affected if The product can load or preview CGM files and the version is affected.

A user is affected if they have JT2Go (any version) or Teamcenter Visualization (versions 13.2.0 through 13.2.0.11, 13.3.0 through 13.3.0.7, 14.0.0 through 14.0.0.3, or 14.1.0 through 14.1.0.5) installed and can open CGM 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 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

Upgrade JT2Go to version V14.1.0.6 or later, and Teamcenter Visualization to the corresponding fixed versions (V13.2.0.12, V13.3.0.8, V14.0.0.4, or V14.1.0.6 depending on the product line). Until patched, avoid opening untrusted CGM files.

Recommended fix High confidence

JT2Go: 14.1.0.6+; Teamcenter Visualization: 13.2.0.12+, 13.3.0.8+, 14.0.0.4+, or 14.1.0.6+ (depending on product line)

  1. Upgrade JT2Go to version 14.1.0.6 or later
  2. Upgrade Teamcenter Visualization V13.2 to version 13.2.0.12 or later
  3. Upgrade Teamcenter Visualization V13.3 to version 13.3.0.8 or later
  4. Upgrade Teamcenter Visualization V14.0 to version 14.0.0.4 or later
  5. Upgrade Teamcenter Visualization V14.1 to version 14.1.0.6 or later
  6. Restart the application after upgrading
Caveat None expected - this is a security patch fix with no described functional changes

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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