dbcve.org
Solid EdgeWeb browser · Siemens

CVE-2023-39181

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 application contains an out of bounds write past the end of an allocated buffer while parsing a specially crafted PAR file. 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 write vulnerability when parsing PAR files. The application writes past the end of an allocated memory buffer during PAR file parsing, leading to memory corruption. An attacker can exploit this by tricking a user into opening a specially crafted PAR file, achieving code execution in the context of the current process.

MitigationUpdate Solid Edge SE2023 to version V223.0 Update 7 or later to obtain the vendor patch. Avoid opening PAR files from untrusted sources until the update is applied.

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. Locate Solid Edge installation directory
    Check common installation paths: C:\Program Files\Siemens\Solid Edge or C:\Program Files (x86)\Siemens\Solid Edge. Verify the folder exists and contains Solid Edge executables.
    Affected if Solid Edge is installed in either location.
  2. Determine installed Solid Edge version
    Right-click on the main executable (typically "SolidEdge.exe") in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, check the version in Add/Remove Programs or the registry under HKLM\SOFTWARE\Siemens\Solid Edge\Setup\InstallDir.
    Affected if The displayed version is SE2023 or earlier (versions prior to V223.0 Update 7).
  3. Identify if PAR file parsing is accessible
    Launch Solid Edge and attempt to open or import a .par file. This can be done via File > Open and selecting PAR files, or by checking if PAR is a recognized file type in the application's Open dialog.
    Affected if PAR files are recognized and the application attempts to parse them (this is enabled by default in vulnerable versions).

A user is affected if Solid Edge SE2023 or any earlier version is installed and the application can parse PAR files, which is the default behavior.

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

Update Solid Edge SE2023 to version V223.0 Update 7 or later to obtain the vendor patch. Avoid opening PAR files from untrusted sources until the update is applied.

Recommended fix High confidence

Solid Edge SE2023 V223.0 Update 7 or later

  1. 1. Check the current Solid Edge version by opening the application and navigating to Help > About Solid Edge
  2. 2. Download Solid Edge SE2023 V223.0 Update 7 or later from the official Siemens support portal (cert-portal.siemens.com)
  3. 3. Close all running instances of Solid Edge
  4. 4. Run the installer for the updated version
  5. 5. Follow the installation wizard prompts to complete the update
  6. 6. Verify the installation by checking Help > About Solid Edge confirms version V223.0 Update 7 or later

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

Fix this in Solid Edge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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