dbcve.org
Solid Edge Se2020 FirmwareOperating system · Siemens

CVE-2021-31342

HIGH · 8.8 CVSS v3.1 Published 2021-06-08
Fix available
A fix is available. Upgrade to 2020mp14 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
The ugeom2d.dll library in all versions of Solid Edge SE2020 before 2020MP14 and all versions of Solid Edge SE2021 before SE2021MP5 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 confidence

The ugeom2d.dll library in Solid Edge SE2020 and SE2021 fails to properly validate user-supplied data when parsing DFT (Draft) files, resulting in an out-of-bounds write past the end of an allocated structure. This memory corruption can be leveraged by an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate Solid Edge SE2020 to version MP14 or later, and SE2021 to version MP5 or later. Until patched, avoid opening untrusted DFT files from unknown sources.

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
Solid Edge Se2020 FirmwareOperating system
Affected:< 2020mp14
Solid Edge Se2021 FirmwareOperating system
Affected:< se2021mp5

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 installed Solid Edge version
    Open Solid Edge, go to Help > About Solid Edge, or check the application version from the installation directory. The version typically displays as SE2020 or SE2021 followed by a build number or MP version.
    Affected if The installed version is SE2020 with a version earlier than MP14, or SE2021 with a version earlier than MP5.
  2. Locate the ugeom2d.dll library
    Navigate to the Solid Edge installation directory (commonly C:\Program Files\Siemens\Solid Edge_<version>) and locate ugeom2d.dll. Right-click the file and select Properties > Details to view the version information.
    Affected if The DLL file exists in the installation, indicating DFT file parsing capability is present.
  3. Verify DFT file parsing capability
    Check if the Solid Edge installation includes the DFT (Draft) file converter or if DFT files can be opened. Attempt to open a DFT file or check File > Open with .dft extension in the supported file types.
    Affected if DFT file parsing is enabled or available in the installation.
  4. Confirm vulnerability condition
    Review the installed version against the affected ranges: SE2020 versions below 2020mp14 and SE2021 versions below se2021mp5 are vulnerable.
    Affected if The installed version falls below the fixed version thresholds and DFT files can be processed.

A user is affected if their Solid Edge installation is SE2020 before MP14 or SE2021 before MP5, and the ugeom2d.dll component with DFT parsing capability is present.

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.

dbcve · scoped
Upgrade available Upgrade to 2020mp14 or later
Fixed in 2020mp14
Interim mitigation

Update Solid Edge SE2020 to version MP14 or later, and SE2021 to version MP5 or later. Until patched, avoid opening untrusted DFT files from unknown sources.

Recommended fix High confidence

Solid Edge SE2020 to version 2020mp14 or later; Solid Edge SE2021 to version se2021mp5 or later

  1. 1. Identify the currently installed Solid Edge version by opening the application and checking Help > About Solid Edge
  2. 2. For Solid Edge SE2020 users: Download and install Solid Edge SE2020 MP14 (or later) from the Siemens Support portal
  3. 3. For Solid Edge SE2021 users: Download and install Solid Edge SE2021 MP5 (or later) from the Siemens Support portal
  4. 4. Verify the patch was applied successfully by checking the version again after installation
  5. 5. As a general precaution, only open DFT files from trusted sources to avoid potential exploits
Caveat Maintenance packs typically include cumulative fixes; review Siemens release notes for any functionality changes or known issues before deployment in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solid Edge Se2020 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31342 — 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-31342 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