Solid Edge Se2023Web browser · Siemens

CVE-2023-49130

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 access vulnerability when parsing specially crafted PAR files. An attacker can exploit this to execute arbitrary code in the context of the current process.

MitigationUpdate Solid Edge SE2023 to version V223.0 Update 10 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:< 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. Identify Solid Edge SE2023 version
    Open the Solid Edge application, then navigate to Help > About Solid Edge, or right-click the SE2023 executable and select Properties to view the version number
    Affected if Version is listed as less than 223.0 or exactly 223.0
  2. Confirm PAR file parsing capability exists
    Attempt to open a .par file in Solid Edge SE2023, or verify the application can import/access PAR file format through File > Open dialog by selecting PAR as a file type
    Affected if PAR file format is available and can be opened in the application
  3. Determine if vulnerable component is loaded
    Check if the native PAR file parser component is present by examining the Solid Edge installation directory for files related to PAR processing, or attempt to load a minimal PAR file to verify the parsing module initializes
    Affected if The PAR file parsing functionality is present and loads when opening PAR files

User is affected if Solid Edge SE2023 version is less than 223.0 or exactly 223.0 AND the application can parse PAR files.

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

Update Solid Edge SE2023 to version V223.0 Update 10 or later to remediate this vulnerability.

Recommended fix High confidence

Solid Edge SE2023 V223.0 Update 10 or later

  1. 1. Determine the current installed version of Solid Edge SE2023 by opening the application and navigating to Help > About Solid Edge
  2. 2. Download Solid Edge SE2023 V223.0 Update 10 (or a later version) from the Siemens cert-portal or official Siemens support channels
  3. 3. Ensure all active Solid Edge sessions are closed before applying the update
  4. 4. Run the downloaded update installer with administrator privileges
  5. 5. Follow the on-screen installation prompts to complete the update
  6. 6. After installation, verify the version by checking Help > About Solid Edge to confirm V223.0 Update 10 or later is installed

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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