dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-24553

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 applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PAR 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

An out-of-bounds read vulnerability exists in Solid Edge SE2022 and SE2023 when parsing specially crafted PAR files. The vulnerability occurs when the parser reads past the end of an allocated memory structure, potentially allowing an attacker to achieve code execution in the context of the current process.

MitigationUpdate Solid Edge SE2022 to version V222.0MP12 or later, and Solid Edge SE2023 to version V223.0Update2 or later to remediate this vulnerability.

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 and version
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SolidEdge\ and read the "Version" or "InstallVersion" value, or check the file version of %ProgramFiles%\Siemens\SolidEdge\bin\Edge3D.dll
    Affected if The installed version is Solid Edge SE2023 with a version number lower than 2210.0002.004
  2. Confirm Solid Edge SE2023 edition
    In Registry, check HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SolidEdge\ for a "ProductName" or "Edition" value, or inspect the program folder name under %ProgramFiles%\Siemens\ to verify it is SE2023 rather than another version
    Affected if The installed product is Solid Edge SE2023 (not SE2022 or another version)
  3. Verify PAR file parsing capability is present
    Check if the PAR file parser module exists by verifying the presence of the file import handler: look for %ProgramFiles%\Siemens\SolidEdge\bin\ParFileHandler.dll or similar PAR-related DLLs in the installation directory
    Affected if PAR file parsing capabilities are installed (this is the feature that triggers the vulnerable code path)

A user is affected if Solid Edge SE2023 is installed with a version lower than 2210.0002.004 and PAR file parsing functionality is present on the system.

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 version V222.0MP12 or later, and Solid Edge SE2023 to version V223.0Update2 or later to remediate this vulnerability.

Recommended fix High confidence

Solid Edge SE2022: V222.0MP12 or higher; Solid Edge SE2023: V223.0Update2 or higher

  1. Upgrade Solid Edge SE2022 to version V222.0MP12 or later
  2. Upgrade Solid Edge SE2023 to version V223.0Update2 or later
  3. Obtain the updates from the official Siemens support portal or through your existing software distribution channel
  4. Verify the installed version after upgrade by checking About Solid Edge in the application

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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