dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-24560

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

An out-of-bounds write vulnerability exists in Solid Edge SE2022 and SE2023 when parsing specially crafted PAR files. The application writes past the end of an allocated buffer during PAR file parsing, leading to memory corruption that can be exploited to execute arbitrary code in the context of the current user process.

MitigationApply vendor patches: 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.

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 installation
    Check for Solid Edge in the program directory (typically C:\Program Files\Siemens\Solid Edge) or look for the application in Add/Remove Programs
    Affected if Solid Edge SE2022 or SE2023 is installed on the system
  2. Identify installed Solid Edge version
    Open Solid Edge, go to Help > About Solid Edge, or check the version in the application's main window. The version number format is like 2210.xxxx.xxxx for SE2023
    Affected if The version displayed is SE2023 with a build earlier than 2210.0002.004, or SE2022 without the V222.0MP12 update
  3. Confirm PAR file parsing capability
    Solid Edge includes native PAR file (part file) parsing for importing legacy part data. This functionality is built into the application and available by default when using File > Open or File > Import on .par files
    Affected if PAR file parsing capability is present and accessible in the installed Solid Edge version
  4. Check application version via Windows registry (alternative method)
    Query the Windows Registry under HKLM\SOFTWARE\Siemens\Solid Edge\CurrentVersion for the Version value, or check HKLM\SOFTWARE\WOW6432Node\Siemens\Solid Edge on 64-bit systems
    Affected if The registry shows a version number lower than 2210.0002.004 for SE2023 installations

A user is affected if Solid Edge SE2023 version is below 2210.0002.004 or SE2022 is without the V222.0MP12 update, and the system can parse PAR files (which is enabled by default).

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

Apply vendor patches: 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

V222.0MP12 for SE2022; V223.0Update2 for SE2023

  1. Identify the currently installed Solid Edge version (SE2022 or SE2023)
  2. For Solid Edge SE2022: Upgrade to version V222.0MP12 or later
  3. For Solid Edge SE2023: Upgrade to version V223.0Update2 (also referred to as V223.0.0Update2) or later
  4. Verify the upgrade was successful by checking the application version

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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