CVE-2022-41284
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 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 confidenceAn out-of-bounds read vulnerability exists in CGM_NIST_Loader.dll when parsing CGM files. This memory corruption flaw allows an attacker to execute arbitrary code 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 Jt2go or Teamcenter Visualization is installedCheck the system for the presence of Siemens Jt2go or Teamcenter Visualization applications. Look in common installation directories (such as Program Files/Siemens) or use system inventory tools to list installed software.Affected if Either Jt2go or Teamcenter Visualization is present on the system
-
Determine the installed version of the Siemens productLocate the main executable (Jt2go.exe for Jt2go or the Teamcenter Visualization binaries) and retrieve its version information. This can be done via file properties, the application's About dialog, or command-line version queries.Affected if The version cannot be determined or the product is present
-
Compare the installed version against affected version rangesFor Jt2go: all versions are affected. For Teamcenter Visualization: check if version is >= 13.2.0 and < 13.2.0.12, OR >= 13.3.0 and < 13.3.0.8, OR >= 14.0 and < 14.0.0.4, OR >= 14.1 and < 14.1.0.6Affected if The installed version falls within any of the affected ranges listed, or for Jt2go, any version is installed
-
Determine if CGM file parsing functionality is accessibleVerify whether the CGM_NIST_Loader.dll module exists within the product installation and whether the application can open or process CGM files. This is the vulnerable component.Affected if CGM file handling is available and the product version is affected
The environment is affected if either Jt2go (any version) or Teamcenter Visualization (specific version ranges) is installed with CGM file parsing enabled and the version matches the affected ranges.
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 JT2Go to version V14.1.0.6 or later, and Teamcenter Visualization to the patched versions (V13.2.0.12, V13.3.0.8, V14.0.0.4, or V14.1.0.6 or later).
JT2Go V14.1.0.6; Teamcenter Visualization V13.2.0.12 / V13.3.0.8 / V14.0.0.4 / V14.1.0.6 (depending on product line)
- 1. Identify the currently installed product: JT2Go or Teamcenter Visualization, and note the specific version number.
- 2. For JT2Go users: Upgrade to version V14.1.0.6 or later.
- 3. For Teamcenter Visualization V13.2 users: Upgrade to version V13.2.0.12 or later.
- 4. For Teamcenter Visualization V13.3 users: Upgrade to version V13.3.0.8 or later.
- 5. For Teamcenter Visualization V14.0 users: Upgrade to version V14.0.0.4 or later.
- 6. For Teamcenter Visualization V14.1 users: Upgrade to version V14.1.0.6 or later.
- 7. After upgrading, verify the CGM_NIST_Loader.dll has been updated and the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41284 — 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-41284 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