CVE-2020-28384
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 PAR files. This could lead to 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 confidenceSolid Edge SE2020 and SE2021 contain a stack-based buffer overflow vulnerability when parsing PAR (parameter) files due to insufficient validation of user-supplied data. An attacker can craft a malicious PAR file that triggers the overflow, allowing arbitrary code execution within the context of the running application.
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.
-
Verify Solid Edge installationCheck for Solid Edge installation by searching for the program in Windows Registry under HKLM\SOFTWARE\Siemens\SolidEdge or HKLM\SOFTWARE\WOW6432Node\Siemens\SolidEdge, or look for the executable at typical installation paths like C:\Program Files\Siemens\SolidEdge<version>\Program\SolidEdge.exeAffected if Solid Edge is not installed on the system
-
Identify installed Solid Edge versionRight-click SolidEdge.exe, select Properties, and view the Details tab for File Version; or query the registry key for the Version value under the installed Solid Edge registry pathAffected if The installed version is SE2020 (any MP before MP12) or SE2021 (any MP before MP2)
-
Confirm PAR file parsing capabilityPAR (parameter) files are a native Solid Edge format for importing part parameters. This functionality exists by default in SE2020 and SE2021 installations - verify by checking if the application can open or import .par files through File > Open or File > ImportAffected if PAR file import functionality is present and enabled in the installation
-
Check for untrusted PAR file processing exposureDetermine if the system processes PAR files from untrusted sources by reviewing Solid Edge file handling settings, recent documents, or network shared folders containing PAR filesAffected if The system has recent or accessible PAR files from potentially untrusted sources
A system is affected if Solid Edge SE2020 (versions before MP12) or SE2021 (versions before MP2) is installed and the PAR file import feature is available, which is the default configuration.
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 vendor-provided patches: upgrade to SE2020MP12 or later for SE2020, and SE2021MP2 or later for SE2021. Alternatively, implement controls to block or restrict untrusted PAR file imports until patches can be applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28384 — 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-28384 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