dbcve.org
Solid EdgeWeb browser · Siemens

CVE-2023-39187

HIGH · 7.8 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
A vulnerability has been identified in Solid Edge SE2023 (All versions < V223.0 Update 7). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted DFT files. This could allow an attacker 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

Solid Edge SE2023 contains an out-of-bounds read vulnerability when parsing specially crafted DFT (design) files. The software reads past the end of an allocated memory structure during file parsing, allowing an attacker who convinces a user to open a malicious DFT file to execute arbitrary code in the context of the current process.

MitigationUpgrade to Solid Edge V223.0 Update 7 or later. Until patched, avoid opening DFT files from untrusted or 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 EdgeWeb browser
Affected:< se2023= se2023

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Solid Edge installation
    Check for Solid Edge in the Windows registry under HKLM\SOFTWARE\Siemens\SolidEdge or look for the application in Program Files (typically C:\Program Files\Siemens\SolidEdge<version>)
    Affected if Solid Edge is installed on the system
  2. Determine installed Solid Edge version
    Open Solid Edge, go to Help > About Solid Edge, or check the version in the registry key HKLM\SOFTWARE\Siemens\SolidEdge\Version
    Affected if The version number is SE2023 or earlier (versions prior to V223.0 Update 7)
  3. Confirm DFT file parsing capability
    Verify that the user works with DFT files by checking recent file access or attempting to open a DFT file through the application
    Affected if DFT files can be opened or imported in the current installation
  4. Check for vulnerable file handlers
    Inspect the file associations for .dft extension in Windows registry under HKCR\.dft or within the Solid Edge application settings
    Affected if The .dft file type is associated with Solid Edge and the software processes these files

A user is affected if Solid Edge SE2023 or earlier is installed and the system can parse DFT files, with the vulnerability present in versions prior to V223.0 Update 7.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Solid Edge V223.0 Update 7 or later. Until patched, avoid opening DFT files from untrusted or unknown sources.

Recommended fix High confidence

Solid Edge V223.0 Update 7 or later

  1. Verify current Solid Edge version by opening the application and navigating to Help > About Solid Edge
  2. Download Solid Edge V223.0 Update 7 or later from the Siemens support portal or your licensed distribution channel
  3. Close all running instances of Solid Edge
  4. Run the installer for the new version and follow the installation wizard prompts
  5. After installation, verify the version by checking Help > About Solid Edge confirms V223.0 Update 7 or later
  6. Test critical DFT file workflows to ensure functionality is preserved

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

Fix this in Solid Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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