dbcve.org
CrosscadwareApplication · Datakit

CVE-2021-27494

HIGH · 7.8 CVSS v3.1 Published 2021-05-27
Fix available
A fix is available. Upgrade to after 2021.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Datakit Software libraries CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr modules in KeyShot Versions v10.1 and prior lack proper validation of user-supplied data when parsing STP files. This could result in a stack-based buffer overflow. An attacker could leverage this vulnerability 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 confidence

Datakit Software libraries used by KeyShot for parsing 3D CAD files (CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr) lack proper validation of user-supplied data when processing STP files. This allows a stack-based buffer overflow where malformed STP input can overwrite stack memory, potentially enabling arbitrary code execution in the context of the current process.

MitigationUpdate KeyShot to a version newer than v10.1 that contains patched Datakit libraries, or implement file upload validation to reject untrusted STP files until a patch is available.

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
CrosscadwareApplication
Affected:<= 2021.1
KeyshotApplication
Affected:<= 10.1
Solid Edge Se2020 FirmwareOperating system
Affected:all versions
Solid Edge Se2021 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify KeyShot version
    Open KeyShot, go to Help > About, or check the Windows Registry under HKLM\SOFTWARE\Luxion\KeyShot or HKLM\SOFTWARE\WOW6432Node\Luxion\KeyShot for the InstallVersion value
    Affected if The installed version is 10.1 or earlier and the software is used to open or process STP files
  2. Identify Datakit Crosscadware version
    Check installed programs list in Windows Control Panel > Programs and Features, or look for Datakit-related DLLs in the application directory and check their properties for version info
    Affected if The installed version is 2021.1 or earlier and STP files are processed through this library
  3. Identify Siemens Solid Edge version
    Open Solid Edge, go to Help > About Siemens Solid Edge, or check the registry under HKLM\SOFTWARE\Siemens\Solid Edge\Version for the Version value
    Affected if The version is Se2020 or Se2021 (any firmware) and STP file import functionality is used
  4. Verify STP parsing modules exist
    Search for the vulnerable DLL modules: CatiaV5_3dRead.dll, CatiaV6_3dRead.dll, Step3dRead.dll, Ug3dReadPsr.dll, Jt3dReadPsr.dll in the application installation directory
    Affected if Any of these DLLs are present and the application uses them to load STP files from untrusted sources
  5. Check for untrusted STP file processing
    Audit workflows where STP files from external or untrusted sources are imported into any of the affected products, particularly automated or web-facing import features
    Affected if STP files from untrusted or external sources are processed by the affected software

You are affected if you run any of the listed products at the specified version ranges AND use them to process STP files, particularly from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2021.1
Interim mitigation

Update KeyShot to a version newer than v10.1 that contains patched Datakit libraries, or implement file upload validation to reject untrusted STP files until a patch is available.

Fix this in Crosscadware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27494 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27494 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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