CVE-2021-27382
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 < SE2020MP13), Solid Edge SE2020 (All versions < SE2020MP14), Solid Edge SE2021 (All Versions < SE2021MP4). Affected applications lack proper validation of user-supplied data when parsing of PAR 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. (ZDI-CAN-13040)
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 stack-based buffer overflow vulnerability exists in Solid Edge's PAR file parser due to insufficient validation of user-supplied data. Attackers can exploit this by crafting malicious PAR files 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<= se2020mp13< se2021mp14CVSS 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 in Program Files (typically C:\Program Files\Siemens\Solid EdgeXXXX) or check registry key HKLM\SOFTWARE\Siemens\Solid Edge for presence of version informationAffected if Solid Edge is not found on the system, the vulnerability does not apply
-
Determine installed Solid Edge versionOpen the registry key HKLM\SOFTWARE\Siemens\Solid Edge\Version or right-click the main Solid Edge executable (solidedge.exe) in the installation folder and view Properties > Details for the File VersionAffected if Cannot determine version - further manual review required
-
Compare version against affected Se2020 rangeIf the installed version is Se2020, note the maintenance pack (MP) number from the version string (e.g., se2020mp13 means MP13). Versions se2020 up to and including MP13 are affectedAffected if Version is Se2020 with MP13 or earlier (e.g., se2020mp1 through se2020mp13)
-
Compare version against affected Se2021 rangeIf the installed version is Se2021, note the maintenance pack number from the version string. Versions se2021 with MP less than MP14 are affectedAffected if Version is Se2021 with MP less than 14 (e.g., se2021mp1 through se2021mp13)
User is affected if Solid Edge Se2020 version is at or below MP13, or Se2021 version is below MP14, and the PAR file parser feature is used.
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-supplied patches: upgrade Solid Edge SE2020 to version SE2020MP13 or later (or SE2020MP14 for the second affected range), and SE2021 to version SE2021MP4 or later.
- 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-2021-27382 — 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-27382 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