dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-49127

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

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

MitigationUpdate Solid Edge SE2023 to version V223.0 Update 10 or later to remediate this vulnerability. Avoid opening untrusted 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. Verify Solid Edge SE2023 is installed
    Check for Solid Edge SE2023 in the Windows Add/Remove Programs list, or look for the installation directory under Program Files or Program Files (x86) typically named 'Solid Edge SE2023'
    Affected if Solid Edge SE2023 is not found on the system, the vulnerability does not apply
  2. Determine the installed version number
    Open Solid Edge SE2023 and go to Help > About Solid Edge, or right-click the executable and select Properties > Details to view the File Version
    Affected if The displayed version is either lower than 223.0 (such as 222.x or earlier) or exactly 223.0 - either condition means the installation is within the affected range
  3. Check for installed updates
    Open Windows Control Panel > Programs and Features, find Solid Edge SE2023, and look at the installed version column or check the application's Help > About dialog for Update version information such as 'Update 10'
    Affected if The version shows Update 9 or earlier, or shows no update information beyond the base 223.0 release, indicating the patch has not been applied
  4. Identify PAR file usage in your workflows
    Review whether you or users in your environment routinely open .par (part) files from external sources or untrusted collaborators using Solid Edge SE2023
    Affected if Users open PAR files from unknown or untrusted sources - this is the attack vector required to trigger the vulnerability

You are affected if Solid Edge SE2023 version 223.0 or any version below 223.0 is installed AND users open PAR files from external or untrusted sources.

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. Avoid opening untrusted PAR files from unknown sources.

Recommended fix High confidence

Solid Edge SE2023 V223.0 Update 10 or later

  1. 1. Identify current Solid Edge SE2023 version by opening the application and navigating to Help > About Solid Edge
  2. 2. Navigate to the Siemens Support Portal (support.industry.siemens.com) or your organization's software distribution system
  3. 3. Locate and download Solid Edge SE2023 Version V223.0 Update 10 or later
  4. 4. Ensure all active Solid Edge instances are closed before installing the update
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the on-screen installation prompts to complete the update
  7. 7. After installation, verify the version by checking Help > About Solid Edge confirms V223.0 Update 10 or higher
  8. 8. Test critical PAR file workflows to ensure functionality is maintained
Caveat Standard upgrade precautions apply - backup custom templates and settings before updating; test in non-production environment first

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
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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