dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-49132

HIGH · 7.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 223.0 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 SE2023 (All versions < V223.0 Update 10). 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 SE2023 contains an uninitialized pointer vulnerability when parsing PAR (part) files. When the application opens a specially crafted malicious PAR file, it accesses an uninitialized pointer, leading to memory corruption that can be leveraged for arbitrary code execution in the context of the current user process.

MitigationUpgrade Solid Edge SE2023 to version V223.0 Update 10 or later to receive the vendor patch that addresses the uninitialized pointer vulnerability in PAR file parsing.

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:< 223.0= 223.0

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 Windows Add/Remove Programs or the program installation directory (typically C:\Program Files\Siemens\Solid Edge SE2023) for the presence of Solid Edge SE2023
    Affected if Solid Edge SE2023 is found on the system
  2. Locate the main Solid Edge executable
    Navigate to the Solid Edge installation folder and locate the main executable file (commonly SE2023.exe or similar), then right-click and select Properties to view the Details tab
    Affected if The executable exists and displays version information
  3. Determine the installed version number
    Read the Product version field from the executable's Properties Details tab, or use the command 'wmic product where "name like 'Solid Edge'" get version' to query installed version
    Affected if Version displays as a number less than 223.0 or exactly 223.0
  4. Confirm vulnerability applicability
    Cross-reference the installed version against the affected range: any version < 223.0 or exactly equal to 223.0 is vulnerable
    Affected if Installed version is < 223.0 or = 223.0

The system is affected if Solid Edge SE2023 is installed with a version number less than 223.0 or exactly 223.0.

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

Upgrade Solid Edge SE2023 to version V223.0 Update 10 or later to receive the vendor patch that addresses the uninitialized pointer vulnerability in PAR file parsing.

Recommended fix High confidence

V223.0 Update 10 or later

  1. Identify current Solid Edge SE2023 version by opening the application and checking Help > About Solid Edge
  2. Navigate to the Siemens Support website or certified portal to download Solid Edge SE2023 Update 10 (V223.0 Update 10) or later
  3. Download the update package from the official Siemens support portal (cert-portal.siemens.com or support.sw.siemens.com)
  4. Close all Solid Edge instances and any related processes
  5. Run the installer and follow the on-screen prompts to apply the update
  6. Restart the application after installation completes
  7. Verify the installed version shows V223.0 Update 10 or higher via Help > About Solid Edge

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