CVE-2022-41285
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 · uneditedA 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 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 confidenceA use-after-free vulnerability exists in CGM_NIST_Loader.dll across multiple Siemens visualization products (JT2Go and Teamcenter Visualization). The vulnerability is triggered when parsing specially crafted CGM files, potentially allowing remote code execution in the context of the current process.
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 dataall versions>= 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.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if JT2Go is installedLook for JT2Go installation directory (typically in Program Files or Program Files (x86)\Siemens\JT2Go) or check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for JT2Go entryAffected if JT2Go is present on the system regardless of version (all versions affected)
-
Check if Teamcenter Visualization is installedLook for Teamcenter Visualization installation directory or check Windows registry under HKLM\SOFTWARE\Siemens\Teamcenter Visualization for installed versionAffected if Teamcenter Visualization is installed with version matching: 13.2.0.x where x < 12, 13.3.0.x where x < 8, 14.0.x where x < 4, or 14.1.x where x < 6
-
Verify installed version of JT2GoOpen JT2Go and go to Help > About, or check the version in the executable properties of JT2Go.exeAffected if Version is any version (all versions of JT2Go are affected)
-
Verify installed version of Teamcenter VisualizationCheck the version of Visualization.exe or run the product and check Help > About, or query registry under the installation path for version infoAffected if Version falls within: 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
-
Confirm CGM file handling capability existsCheck if CGM_NIST_Loader.dll exists in the product installation directory (typically in bin folder under the main installation path)Affected if The vulnerable DLL is present and the product can be used to open CGM files
A user is affected if they have JT2Go of any version installed, or Teamcenter Visualization with version 13.2.0.x before 12, 13.3.0.x before 8, 14.0.x before 4, or 14.1.x before 6, and the CGM_NIST_Loader.dll is available for parsing CGM files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.2.0.1213.3.0.814.0.0.4
Apply vendor patches by upgrading to JT2Go V14.1.0.6, Teamcenter Visualization V13.2.0.12, V13.3.0.8, V14.0.0.4, or V14.1.0.6 respectively. Consider disabling CGM file handling or restricting file sources until patches are applied.
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
- Identify the currently installed version of JT2Go or Teamcenter Visualization
- Determine which product line and version is affected (JT2Go or Teamcenter Visualization specific version)
- For JT2go: Upgrade to version 14.1.0.6 or later
- For Teamcenter Visualization V13.2: Upgrade to version 13.2.0.12 or later
- For Teamcenter Visualization V13.3: Upgrade to version 13.3.0.8 or later
- For Teamcenter Visualization V14.0: Upgrade to version 14.0.0.4 or later
- For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.6 or later
- Obtain the updated software from the official Siemens support portal or certified distribution channels
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41285 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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