dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-24551

HIGH · 7.8 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 2210.0002.004 or later.
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 SE2022 (All versions < V222.0MP12), Solid Edge SE2023 (All versions < V223.0Update2). The affected application is vulnerable to heap-based buffer underflow while parsing specially crafted PAR files. 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

Heap-based buffer underflow vulnerability in Solid Edge allows remote code execution when parsing specially crafted PAR files. The vulnerability stems from improper bounds checking during file parsing, enabling an attacker to write before the allocated buffer memory.

MitigationUpdate Solid Edge SE2022 to V222.0MP12 or later, and SE2023 to V223.0Update2 or later. Until patched, avoid opening PAR files from untrusted 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 Se2023Web browser
Affected:< 2210.0002.004

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
    Search for Solid Edge installation directory in C:\Program Files\Siemens\ or check Windows Programs and Features (Add or Remove Programs) for Siemens Solid Edge entries
    Affected if Solid Edge is not installed - not affected
  2. Identify exact version number
    Right-click the main Solid Edge executable (usually solid Edge.exe in the installation folder), select Properties, and read the File Version from the Details tab. Alternatively, launch Solid Edge and navigate to Help > About Solid Edge
    Affected if Cannot determine version number from executable or application
  3. Verify SE2023 version against affected range
    For Solid Edge SE2023, compare the installed version to 2210.0002.004. If the version string starts with 2210 and the build is below 0002.004, or if it is any earlier 2210.x.x build, it is within the affected range
    Affected if Installed SE2023 version is below 2210.0002.004 AND users open PAR files
  4. Confirm PAR file handling capability
    PAR files are native to Solid Edge - the parsing functionality is built into the application and requires no special configuration. Simply having the ability to open or import PAR files indicates the affected code path exists
    Affected if Solid Edge can open or import PAR files (this is enabled by default in the installed product)

Environment is affected if Solid Edge SE2023 version is below 2210.0002.004 (or SE2022 below 222.0MP12) and users can open PAR files, as the vulnerable code path executes during PAR file parsing.

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 2210.0002.004 or later
Fixed in 2210.0002.004
Interim mitigation

Update Solid Edge SE2022 to V222.0MP12 or later, and SE2023 to V223.0Update2 or later. Until patched, avoid opening PAR files from untrusted sources.

Recommended fix High confidence

Solid Edge SE2022: V222.0MP12 or later; Solid Edge SE2023: V223.0Update2 (2210.0002.004) or later

  1. 1. Identify the current installed version of Solid Edge (SE2022 or SE2023) by opening the application and checking Help > About Solid Edge
  2. 2. For Solid Edge SE2022 users: Download and install version V222.0MP12 or later from the Siemens support portal (support.industry.siemens.com)
  3. 3. For Solid Edge SE2023 users: Download and install version V223.0Update2 (build 2210.0002.004) or later from the Siemens support portal
  4. 4. Verify the installation was successful by checking the version number in Help > About Solid Edge
  5. 5. Apply the update to all systems that have Solid Edge installed, particularly those that handle PAR files from external sources
Caveat Standard version upgrade - review Siemens release notes for any new features or workflow changes that may affect existing templates or workflows

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

Fix this in Solid Edge Se2023 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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