CVE-2021-22643
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 · uneditedLuxion KeyShot versions prior to 10.1, Luxion KeyShot Viewer versions prior to 10.1, Luxion KeyShot Network Rendering versions prior to 10.1, and Luxion KeyVR versions prior to 10.1 are vulnerable to an out-of-bounds read while processing project files, which may allow an attacker to execute arbitrary code.
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 confidenceKeyShot software versions prior to 10.1 contain an out-of-bounds read vulnerability when parsing project files, which can lead to arbitrary code execution. This memory safety issue allows reading beyond allocated buffer boundaries, potentially exposing sensitive data or enabling control-flow manipulation.
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< 10.1< 10.1< 10.1< 10.1all versionsall versionsCVSS 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 KeyShot productsSearch the system for KeyShot executables. Common locations: C:\Program Files\KeyShot* or C:\Program Files (x86)\KeyShot*. Check Add/Remove Programs for KeyShot, KeyShot Viewer, KeyShot Network Rendering, or KeyVR installations.Affected if Any KeyShot product is found on the system
-
Determine installed KeyShot versionRight-click the KeyShot executable, select Properties, then go to the Details tab. Look for 'File version' or 'Product version'. Alternatively, launch KeyShot and check Help > About KeyShot.Affected if The version shown is earlier than 10.1 (for example, 10.0, 9.x, 8.x, etc.)
-
Check for Siemens Solid Edge installationsSearch for Solid Edge executables in C:\Program Files\Siemens\ or check Add/Remove Programs for Siemens Solid Edge.Affected if Siemens Solid Edge SE2020 or SE2021 is installed (all versions are affected per the advisory)
-
Verify project file parsing exposureDetermine if users routinely open .keyshot, .ksp, or other KeyShot project files from external or untrusted sources. Check for recent project files in common document folders.Affected if The software processes project files and the version is below 10.1 or Solid Edge SE2020/SE2021 is present
If KeyShot, KeyShot Viewer, KeyShot Network Rendering, or KeyVR version is below 10.1, OR if Siemens Solid Edge SE2020 or SE2021 is installed, the environment is vulnerable to CVE-2021-22643.
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.
From vendor data10.1
Upgrade all KeyShot products (KeyShot, KeyShot Viewer, KeyShot Network Rendering, and KeyVR) to version 10.1 or later to patch the vulnerability.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22643 — 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-2021-22643 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