CVE-2021-27492
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 · uneditedWhen opening a specially crafted 3DXML file, the application containing Datakit Software libraries CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr modules in KeyShot Versions v10.1 and prior could disclose arbitrary files to remote attackers. This is because of the passing of specially crafted content to the underlying XML parser without taking proper restrictions such as prohibiting an external DTD.
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 v10.1 and prior contains vulnerable XML parsing code in Datakit libraries (CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr) that processes 3DXML files without disabling external DTD entities, allowing XXE injection to read arbitrary files from the system.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 versionCheck the installed version of Luxion KeyShot (typically via Help > About or the installer/windows program listing)Affected if The installed version is 10.1 or prior (e.g., 10.0, 9.x, etc.)
-
Identify installed Datakit Crosscadware versionCheck the Datakit Crosscadware version if installed as a plugin or standalone (check program files or the application's plugin manager)Affected if The version is 2021.1 or prior
-
Confirm presence of vulnerable Datakit 3DXML modulesLook for the Datakit libraries (CatiaV5_3dRead, CatiaV6_3dRead, Step3dRead, Ug3dReadPsr, Jt3dReadPsr) in the KeyShot or Datakit installation directoryAffected if These specific Datakit 3DXML parsing modules are present on the system
-
Check if Siemens Solid Edge is installed with vulnerable versionsIdentify if Siemens Solid Edge SE2020 or SE2021 is installed (check Windows program list or installation directory)Affected if Either Solid Edge SE2020 or SE2021 is installed (all versions of these firmwares are affected)
-
Verify 3DXML file import capability is in useCheck if users have access to or are importing 3DXML files through the affected products, or examine file associations for .3dxml file typeAffected if 3DXML file import functionality is available and users process 3DXML files with the affected software
A system is affected if it runs KeyShot <=10.1, Datakit Crosscadware <=2021.1, Solid Edge SE2020, or Solid Edge SE2021 and uses the Datakit 3DXML parsing modules to process 3DXML files.
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 dataUpdate KeyShot to a version that has patched the XXE vulnerability in the Datakit 3DXML parsing modules; until then, avoid opening untrusted 3DXML files from unknown sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27492 — 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-27492 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