dbcve.org
Solid Edge Se2024Web browser · Siemens

CVE-2024-33490

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 224.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 (All versions < V224.0 Update 5). 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 versions prior to V224.0 Update 5 contain an out-of-bounds read vulnerability in the PAR file parser. When parsing specially crafted PAR files, the application reads past the end of an allocated memory structure, leading to memory corruption that can be leveraged for arbitrary code execution in the context of the current process.

MitigationUpdate Solid Edge to V224.0 Update 5 or later to obtain the vendor patch. Until patched, avoid opening PAR files from untrusted 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 Se2024Web browser
Affected:< 224.0= 224.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. Confirm Solid Edge installation
    Locate the Solid Edge installation directory or check Program Files for Siemens Solid Edge folder. On Windows, verify the program exists in the installed applications list.
    Affected if Solid Edge is not installed on the system, this CVE does not apply.
  2. Identify installed Solid Edge version
    Check the version of the installed Solid Edge executable. This can typically be found by right-clicking the main executable (usually named solid edge.exe or similar), selecting Properties, and viewing the File Version field. Alternatively, check the version information in the Windows registry under the Solid Edge installation keys.
    Affected if Unable to determine the version - further investigation needed to assess exposure.
  3. Compare version against affected range
    Review the identified version number. The affected versions are any release prior to V224.0 Update 5, including version 224.0 itself. Determine if your installed version falls into this category.
    Affected if Installed version is less than 224.0 OR equals exactly 224.0 - the environment is vulnerable to this issue.
  4. Assess PAR file processing exposure
    Determine if the Solid Edge installation is used to open or process PAR files. This vulnerability is triggered specifically when parsing specially crafted PAR files. Check if users routinely open PAR files from external or untrusted sources.
    Affected if Vulnerable version AND the ability to process PAR files exists - the attack vector is present.

A system is affected if it runs Solid Edge version 224.0 or any version prior to V224.0 Update 5, and that installation can be used to open or process 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 224.0 or later
Fixed in 224.0
Interim mitigation

Update Solid Edge to V224.0 Update 5 or later to obtain the vendor patch. Until patched, avoid opening PAR files from untrusted sources.

Recommended fix High confidence

Solid Edge V224.0 Update 5 or later

  1. Backup all critical Solid Edge files, templates, and custom configurations
  2. Navigate to the official Siemens support portal or cert-portal.siemens.com to obtain the V224.0 Update 5 patch or later
  3. Download the Solid Edge V224.0 Update 5 installer or patch file
  4. Close all running Solid Edge applications and related processes
  5. Execute the installer and follow the on-screen prompts to apply the update
  6. Restart the system after installation completes
  7. Launch Solid Edge and verify the application runs without errors
  8. Test opening existing PAR files to confirm the vulnerability is remediated
Caveat Standard upgrade risk: review release notes for any changes to file format compatibility or deprecated features before deploying to production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solid Edge Se2024 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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