CVE-2022-41286
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 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 confidenceA memory corruption vulnerability exists in CGM_NIST_Loader.dll when parsing malformed CGM files. The out-of-bounds write allows an attacker to achieve code execution in the context of the current process by tricking a user into opening a specially crafted CGM file.
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.
-
Identify if Siemens Jt2go is installedCheck for Jt2go installation directory, typically under C:\Program Files\Siemens\Jt2go or C:\Program Files (x86)\Siemens\Jt2go. On Linux/Mac, check /usr/local/Siemens/Jt2go or ~/Applications/Siemens/Jt2go.Affected if Jt2go is present on the system regardless of version (all versions are affected)
-
Identify if Siemens Teamcenter Visualization is installedCheck for Teamcenter Visualization installation, typically under C:\Program Files\Siemens\Teamcenter<version>\Visualization or within the Teamcenter installation directory structure.Affected if Teamcenter Visualization is present on the system with a version in the affected ranges: 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
-
Locate the vulnerable DLL CGM_NIST_Loader.dllSearch for CGM_NIST_Loader.dll within the product installation directories. Common paths include <install_dir>\bin\ or <install_dir>\Program\. Use file system search or command: dir /s C:\CGM_NIST_Loader.dllAffected if The DLL exists in the product installation directory, confirming the vulnerable component is present
-
Determine installed product versionAccess the product version through Windows Registry: HKLM\SOFTWARE\Siemens\JT2Go\ProductVersion or HKLM\SOFTWARE\Siemens\Teamcenter Visualization\ProductVersion. Alternatively, right-click the executable and select Properties > Details for version information.Affected if The version number falls within the affected ranges listed for Teamcenter Visualization, or is any version of Jt2go
A user is affected if they have Siemens Jt2go (any version) or Siemens Teamcenter Visualization in versions 13.2.0-11, 13.3.0-7, 14.0.0-3, or 14.1.0-5 installed, with the CGM_NIST_Loader.dll component present.
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-supplied patches to update JT2Go to V14.1.0.6 or later, and Teamcenter Visualization to the fixed versions (V13.2.0.12, V13.3.0.8, V14.0.0.4, or V14.1.0.6). Coordinate patch deployment through standard change management and validate functionality post-update.
Jt2Go: V14.1.0.6+ | Teamcenter Visualization: V13.2.0.12+, V13.3.0.8+, V14.0.0.4+, or V14.1.0.6+ depending on branch
- 1. Identify which product is in use: Jt2Go or Teamcenter Visualization
- 2. If using Jt2Go: upgrade to version 14.1.0.6 or later
- 3. If using Teamcenter Visualization V13.2.x: upgrade to version 13.2.0.12 or later
- 4. If using Teamcenter Visualization V13.3.x: upgrade to version 13.3.0.8 or later
- 5. If using Teamcenter Visualization V14.0.x: upgrade to version 14.0.0.4 or later
- 6. If using Teamcenter Visualization V14.1.x: upgrade to version 14.1.0.6 or later
- 7. Verify the update was applied by checking the application's About/Help section for the version number
- 8. Test that CGM file parsing functionality works correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41286 — 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-41286 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