CVE-2021-22649
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 have multiple NULL pointer dereference issues 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 confidenceMultiple NULL pointer dereference vulnerabilities exist in Luxion KeyShot, KeyShot Viewer, KeyShot Network Rendering, and KeyVR (versions prior to 10.1) when processing malicious project files. These memory corruption flaws may allow an attacker to achieve arbitrary code execution via specially crafted .ksp or other project file formats.
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 Luxion productCheck the installed programs list in Windows Control Panel or Program Files folder for KeyShot, KeyShot Viewer, KeyShot Network Rendering, or KeyVR. Also check for Siemens Solid Edge SE2020 or SE2021.Affected if Any of these products are installed, proceed to version check.
-
Determine KeyShot product versionRight-click the installed KeyShot executable (typically in C:\Program Files\Luxion\KeyShot# or similar path), select Properties, and view the Version tab. Alternatively, run the application and check Help > About.Affected if Version is less than 10.1 (e.g., 10.0, 9.x, 8.x, etc.) indicates the product is affected.
-
Determine Siemens Solid Edge versionOpen Siemens Solid Edge and navigate to Help > About, or check the installation directory for version information.Affected if Any version of Solid Edge SE2020 or SE2021 is installed (all versions are affected per the CVE).
-
Verify project file handling is possibleConfirm the software can open or import .ksp project files or other file formats. Check File > Open or File > Import menu options.Affected if The software can process project files and the version is in the affected range, the vulnerability is applicable.
If any KeyShot product version is below 10.1 or any Siemens Solid Edge SE2020/SE2021 is installed and the software can open project files, the environment is affected by this CVE.
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 to address the NULL pointer dereference vulnerabilities.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22649 — 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-22649 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