dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-24549

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 stack-based buffer 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

Stack-based buffer overflow vulnerability in Solid Edge PAR file parser. Specially crafted PAR files can cause memory corruption leading to arbitrary code execution in the context of the current process.

MitigationApply vendor patches: update Solid Edge SE2022 to V222.0MP12 or later, or SE2023 to V223.0Update2 or later.

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. Identify installed Solid Edge version
    Check the Solid Edge installation by examining the executable properties of the main program (typically located in C:\Program Files\Siemens\Solid EdgeXXXX\Program\Edge.exe) or via Windows Registry at HKLM\SOFTWARE\Siemens\Solid Edge\Version
    Affected if The installed version is Solid Edge Se2023 and is earlier than 2210.0002.004
  2. Confirm SE2023 product line
    Verify the product version string returned from the version check clearly indicates the SE2023 release line (such as Se2023, 2210, or similar notation indicating the 2023 release)
    Affected if The product identifies as SE2023 (2023 release) rather than other release years
  3. Validate PAR file parser availability
    Confirm that the PAR file parser component exists in the Solid Edge installation by checking for the presence of related file parsing libraries or by attempting to access the PAR file import functionality within the application
    Affected if PAR file parsing functionality is present and accessible in the installed version
  4. Compare version against affected range
    Extract the full version number (including build/subversion like 2210.0002.004) and compare numerically to the threshold 2210.0002.004
    Affected if The version number is less than 2210.0002.004 (for example, 2210.0001.005 or earlier)

A user is affected if Solid Edge SE2023 is installed with a version number lower than 2210.0002.004 and the PAR file parser component is accessible.

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, or SE2023 to V223.0Update2 or later.

Recommended fix High confidence

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

  1. Check current Solid Edge version via Help > About Solid Edge
  2. Navigate to Siemens Support Portal (support.sw.siemens.com) or your organization's software distribution system
  3. Download Solid Edge SE2023 version V223.0Update2 or later (or SE2022 version V222.0MP12 or later for that product line)
  4. Close all Solid Edge instances and any related processes
  5. Run the installer with appropriate administrative privileges
  6. Follow the installation wizard prompts to complete the update
  7. Verify the installed version matches the expected fixed release

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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