dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-49126

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

Solid Edge SE2023 contains an out-of-bounds read vulnerability when parsing PAR files. The vulnerability occurs when the parser reads past the end of an allocated structure, potentially allowing an attacker to execute arbitrary code in the context of the current process.

MitigationUpgrade to Solid Edge V223.0 Update 10 or later to remediate this vulnerability. Additionally, avoid opening untrusted or specially crafted PAR files from unknown 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:< 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 installation
    Open Windows Control Panel > Programs and Features, or the Settings > Apps & Features page, and locate Siemens Solid Edge SE2023 in the installed programs list.
    Affected if Solid Edge SE2023 is installed on the system
  2. Determine the installed version number
    In the Programs and Features list, click on Solid Edge SE2023 to view the version, or right-click the main Solid Edge executable (typically in C:\Program Files\Siemens\Solid Edge2023\Program\Edge.exe) and select Properties > Details to see the File Version.
    Affected if The version shown is 223.0 or any version lower than 223.0 (for example, 222.0, 221.0, etc.)
  3. Confirm the PAR file parser is accessible
    Verify that the Solid Edge installation includes the capability to open PAR (parametric) files, which is standard functionality in Solid Edge. PAR files are native to the software and the parser is part of the core application.
    Affected if Solid Edge SE2023 can open PAR files, meaning the vulnerable parser component is present and active in the installation

The environment is affected if Solid Edge SE2023 version 223.0 or any version below 223.0 is installed and the PAR file parsing feature is available.

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 to Solid Edge V223.0 Update 10 or later to remediate this vulnerability. Additionally, avoid opening untrusted or specially crafted PAR files from unknown sources.

Recommended fix High confidence

Solid Edge SE2023 V223.0 Update 10 or later

  1. Back up all Solid Edge SE2023 files, custom templates, and user settings before proceeding with the update
  2. Obtain Solid Edge SE2023 V223.0 Update 10 (or later) from the official Siemens support portal or your authorized Siemens distributor
  3. Close all running Solid Edge instances and ensure no related processes are active
  4. Run the installer for V223.0 Update 10 with administrator privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. After installation, verify the version by launching Solid Edge and checking Help > About Solid Edge confirms V223.0 Update 10 or later is installed
  7. Re-apply any custom configurations or third-party add-ins that were in use, as these may need reinstallation or reconfiguration
Caveat Minimal risk expected as this is a point update within the same major version; however, validate critical workflows and custom templates after upgrade

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