CVE-2020-28386
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 · uneditedA vulnerability has been identified in Solid Edge SE2020 (All Versions < SE2020MP12), Solid Edge SE2021 (All Versions < SE2021MP2). Affected applications lack proper validation of user-supplied data when parsing DFT files. This could result in an out of bounds write past the end of an allocated structure. 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 confidenceA vulnerability exists in Solid Edge SE2020 and SE2021 where the application fails to properly validate user-supplied data when parsing DFT (drawing) files. This insufficient validation allows an out-of-bounds write operation beyond the allocated memory structure, which can be leveraged by an attacker to achieve arbitrary code execution within the context of the current process.
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< se2020= se2020= se2021CVSS 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 if Solid Edge is installedLook for Solid Edge installation directory, typically in Program Files or Program Files (x86) folder, or check Windows Registry under HKLM\SOFTWARE\Siemens\SolidEdge and HKLM\SOFTWARE\WOW6432Node\Siemens\SolidEdge for the installation pathAffected if Solid Edge is not found on the system, then this CVE does not apply
-
Identify the installed Solid Edge versionOpen Solid Edge and go to Help > About Solid Edge, or check the version in the registry key HKLM\SOFTWARE\Siemens\SolidEdge\Version (or the WOW6432Node equivalent), or look at the executable properties of solidedge.exe in the installation folderAffected if The version displayed is SE2020 or SE2021 (before the maintenance packs MP12 for SE2020 and MP2 for SE2021)
-
Confirm the DFT file parsing feature is presentVerify that the Solid Edge installation includes the DFT (Drawing File Template) component by checking for DFT-related files or by attempting to open a DFT file through the applicationAffected if Solid Edge can open or process DFT files and the version is SE2020 or SE2021 before the fixed maintenance packs
A user is affected if Solid Edge SE2020 or SE2021 is installed with a version prior to MP12 (for SE2020) or MP2 (for SE2021) and the application is used to open DFT files from potentially untrusted sources.
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 dataApply the vendor-supplied patches: upgrade to Solid Edge SE2020 MP12 or later, or SE2021 MP2 or later. Until patches are applied, avoid opening DFT files from untrusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28386 — 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-2020-28386 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