CVE-2022-41664
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.4), Teamcenter Visualization V13.2 (All versions < V13.2.0.12), Teamcenter Visualization V13.3 (All versions < V13.3.0.7), Teamcenter Visualization V14.0 (All versions < V14.0.0.3), Teamcenter Visualization V14.1 (All versions < V14.1.0.4). The affected application contains a stack-based buffer overflow vulnerability that could be triggered while parsing specially crafted PDF files. This could allow an attacker 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 confidenceStack-based buffer overflow vulnerability in the PDF parsing component of JT2Go and Teamcenter Visualization software. Specially crafted PDF files can trigger overflow, allowing attackers to execute arbitrary code 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 data< 14.1.0.4>= 13.3.0, < 13.3.0.7>= 14.0, < 14.0.0.3>= 14.1, < 14.1.0.4CVSS 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 installed Siemens visualization productCheck Windows Programs and Features, or locate the application executable (JT2Go.exe for JT2Go, or the Teamcenter Visualization binaries). The product name will be either 'Siemens JT2Go' or 'Siemens Teamcenter Visualization'.Affected if The product is either JT2Go or Teamcenter Visualization
-
Determine installed version of the productRight-click the application's main executable, select Properties, and check the 'Version' tab. Alternatively, check the Windows registry under HKLM\SOFTWARE\Siemens\JT2Go or HKLM\SOFTWARE\Siemens\Teamcenter Visualization for the installed version value.Affected if The version cannot be determined or is lower than the fixed releases
-
Compare against affected version rangesFor JT2Go: version must be >= 14.1.0.4 to be fixed. For Teamcenter Visualization: fixed versions are 13.3.0.7, 14.0.0.3, and 14.1.0.4. Any version below these thresholds in their respective branches is vulnerable.Affected if JT2Go version < 14.1.0.4 OR Teamcenter Visualization version is 13.3.x below 13.3.0.7, 14.0.x below 14.0.0.3, or 14.1.x below 14.1.0.4
-
Verify PDF processing capability is presentConfirm the software has PDF import or viewing functionality enabled. This is a native feature in these products, so the vulnerability applies if the software is installed and can open PDF files.Affected if The software can process PDF files as part of its normal functionality
You are affected if you have JT2Go or Teamcenter Visualization installed with a version below the fixed releases (14.1.0.4 for JT2Go; 13.3.0.7, 14.0.0.3, or 14.1.0.4 for Teamcenter Visualization depending on your branch).
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.3.0.714.0.0.314.1.0.4
Apply vendor-supplied patches: upgrade JT2Go to V14.1.0.4 or later, Teamcenter Visualization V13.2 to V13.2.0.12, V13.3 to V13.3.0.7, V14.0 to V14.0.0.3, and V14.1 to V14.1.0.4. Alternatively, restrict or disable PDF processing until patching is feasible.
JT2Go: 14.1.0.4+ | Teamcenter Visualization: 13.2.0.12+, 13.3.0.7+, 14.0.0.3+, or 14.1.0.4+ depending on current branch
- Identify the specific product (JT2Go or Teamcenter Visualization) and current version installed
- For JT2Go: Upgrade to version 14.1.0.4 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.7 or later
- For Teamcenter Visualization V14.0: Upgrade to version 14.0.0.3 or later
- For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.4 or later
- Obtain the update from the official Siemens cert-portal or Siemens support channels
- Verify the vulnerability is remediated by testing with the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41664 — 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-41664 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