CVE-2021-27490
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 · uneditedDatakit Software libraries CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr modules in KeyShot Versions v10.1 and prior are vulnerable to an out-of-bounds read, 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 confidenceOut-of-bounds read vulnerability in Datakit Software libraries (CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr) used by KeyShot v10.1 and prior allows reading beyond allocated memory boundaries, potentially enabling arbitrary code execution through malicious 3D model files.
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<= 2021.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.
-
Check KeyShot versionLocate KeyShot installation and check the version (typically found in the application properties, 'About' dialog, or installer information)Affected if Version is 10.1 or earlier (any version <= 10.1)
-
Check Datakit Crosscadware versionLocate Datakit Crosscadware installation and check the version number (check installer information or application metadata)Affected if Version is 2021.1 or earlier (any version <= 2021.1)
-
Identify vulnerable Datakit librariesSearch for the presence of the affected library files: CatiaV5_3dRead.dll, CatiaV6_3dRead.dll, Step3dRead.dll, Ug3dReadPsr.dll, or Jt3dReadPsr.dll within the application directoriesAffected if Any of these specific library files are present in the KeyShot or Datakit installation directories
-
Check Siemens Solid Edge installationDetermine if Siemens Solid Edge SE2020 or SE2021 is installed (check program files or application inventory)Affected if Solid Edge SE2020 or SE2021 is installed (all versions of these products are affected)
-
Verify library usageIf the above libraries are present, confirm they are actively used by the application for 3D model import functionalityAffected if The application uses these libraries to import 3D model files (Catia, Step, UG, or Jt formats)
You are affected if you have KeyShot <= 10.1, Datakit Crosscadware <= 2021.1, or Solid Edge SE2020/SE2021 installed, with the vulnerable Datakit libraries present and enabled for 3D model processing.
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 dataUpgrade KeyShot to a version newer than v10.1 that includes patched Datakit libraries; avoid opening untrusted 3D model files until the update is applied.
- Consultation2.0 h
- Implementation2.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 $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27490 — 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-27490 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