dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-24563

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 uninitialized pointer access 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

Solid Edge is vulnerable to an uninitialized pointer access vulnerability when parsing specially crafted PAR (part) files. This memory corruption issue allows an attacker to execute arbitrary code in the context of the current process by convincing a user to open a malicious PAR file.

MitigationUpgrade Solid Edge SE2022 to V222.0MP12 or later, and SE2023 to V223.0Update2 or later. Alternatively, avoid opening untrusted PAR 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 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. Verify Solid Edge Se2023 is installed
    Check for Solid Edge installation directory (typically C:\Program Files\Siemens\Solid Edge Se2023) or look in Windows Registry under HKLM\SOFTWARE\Siemens\Solid Edge\Se2023
    Affected if Solid Edge Se2023 is found on the system
  2. Determine installed Solid Edge version
    Open Solid Edge, go to Help > About, or right-click the main executable (Edge.exe) and select Properties > Details to view the File Version
    Affected if Version displayed is less than 2210.0002.004 (for example, 2210.0001.001 or earlier)
  3. Confirm PAR file parsing capability is present
    Solid Edge naturally includes PAR (part file) parsing as core functionality - verify by attempting to open any .par file within the application
    Affected if The application can open and parse PAR files (this is the default behavior and the attack vector)
  4. Compare version against CVE threshold
    If version cannot be obtained via GUI, check registry key HKLM\SOFTWARE\Siemens\Solid Edge\Se2023\Version or examine the version resource of Edge.exe using a tool like strings or a PE viewer
    Affected if The installed version string is lexicographically or numerically lower than 2210.0002.004

If Solid Edge Se2023 is installed with a version below 2210.0002.004 and can parse PAR files, the environment is vulnerable to this CVE.

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

Upgrade Solid Edge SE2022 to V222.0MP12 or later, and SE2023 to V223.0Update2 or later. Alternatively, avoid opening untrusted PAR files from unknown sources.

Recommended fix High confidence

Solid Edge SE2022: upgrade to V222.0MP12 or later; Solid Edge SE2023: upgrade to V223.0Update2 (2210.0002.004) 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 SE2022 users: Download and install version V222.0MP12 or later from the Siemens support portal (cert-portal.siemens.com)
  3. 3. For Solid Edge SE2023 users: Download and install version V223.0Update2 (also referenced as 2210.0002.004 or later) from the Siemens support portal
  4. 4. Verify the installation was successful by checking the version in Help > About Solid Edge matches the patched release
  5. 5. Test that PAR file parsing functionality works normally with the updated version
Caveat Standard upgrade considerations apply - review Siemens release notes for any workflow or compatibility changes between versions

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

Fix this in Solid Edge Se2023 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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