CVE-2021-22645
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 attack because the .bip documents display a “load” command, which can be pointed to a .dll from a remote network share. As a result, the .dll entry point can be executed without sufficient UI warning.
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 confidenceThis is a DLL hijacking vulnerability in Luxion KeyShot software where specially crafted .bip documents contain a 'load' command that can reference DLLs from remote network shares. When a user opens a malicious .bip file, the application loads the specified DLL without sufficient validation or user warning, allowing arbitrary code execution.
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 product versionCheck the installed version of KeyShot (or KeyShot Viewer, KeyShot Network Rendering, KeyVR) via the application's About dialog, installed program properties, or registry key under HKLM\SOFTWARE\Luxion\KeyShot (or respective product)Affected if The installed version is lower than 10.1 for any KeyShot product
-
Confirm .bip file handling capabilityVerify that the installed software can open or process .bip files - check file type associations, recent documents, or attempt to identify if .bip is a supported format for the installed productAffected if The software is configured to handle .bip files and the version is vulnerable
-
Identify Siemens Solid Edge installationCheck for installation of Siemens Solid Edge SE2020 or SE2021 on the system - look in Program Files for Siemens folder, or check Add/Remove Programs for Solid Edge entriesAffected if Siemens Solid Edge SE2020 or SE2021 is installed (all versions are affected)
-
Check for network share accessibilityVerify if the system has access to remote network shares or UNC paths that could host malicious DLLs - review mapped network drives or accessible UNC pathsAffected if The system can access remote/network shares and runs vulnerable KeyShot software
A system is affected if it has any KeyShot product version below 10.1 or Siemens Solid Edge SE2020/SE2021 installed, and the software processes .bip files or has network share access.
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 affected KeyShot products (KeyShot, KeyShot Viewer, KeyShot Network Rendering, KeyVR) to version 10.1 or later. Additionally, disable or restrict access to untrusted network shares and avoid opening .bip files from untrusted sources.
- Consultation2.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 $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22645 — 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-22645 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