dbcve.org
ParasolidApplication · Siemens

CVE-2024-54091

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 36.1.225 / 37.0.173 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 SE2024 (All versions < V224.0 Update 12), Solid Edge SE2025 (All versions < V225.0 Update 3). The affected application contains an out of bounds write past the end of an allocated buffer while parsing X_T data or a specially crafted file in X_T format. 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

A memory corruption vulnerability exists in Solid Edge SE2024 and SE2025 when parsing X_T files. The application performs an out-of-bounds write past the end of an allocated buffer during X_T file parsing, allowing an attacker to achieve code execution in the context of the current process via a specially crafted malicious X_T file.

MitigationUpdate Solid Edge SE2024 to version V224.0 Update 12 or later, and SE2025 to V225.0 Update 3 or later. Until patched, avoid opening X_T files from untrusted sources and run the application with reduced privileges to limit impact of potential exploitation.

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
ParasolidApplication
Affected:>= 36.1, < 36.1.225>= 37.0, < 37.0.173
Solid Edge Se2024Web browser
Affected:all versions= 224.0
Solid Edge Se2025Web browser
Affected:all versions= 225.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 product version
    Open Solid Edge, go to Help > About Solid Edge, or check the installation directory for version information. Look for the SE2024 or SE2025 release version (such as V224.0 or V225.0).
    Affected if The installed version is SE2024 (any build) or SE2025 (any build), or specifically versions prior to V224.0 Update 12 or V225.0 Update 3.
  2. Check Parasolid version number
    In Solid Edge, access the Parasolid version information through Help > About or the application log files. Parasolid versions typically appear as a numeric build such as 36.1.x or 37.0.x.
    Affected if Parasolid version is 36.1.x and below 36.1.225, or 37.0.x and below 37.0.173.
  3. Determine if X_T file import is used
    Check recent import operations or file history within Solid Edge for .x_t file imports. Look in recent documents, job logs, or the application event log for X_T file access.
    Affected if The application has recently imported or opened X_T files from any source.
  4. Review installed hotfixes or updates
    Check the Solid Edge installation for installed updates. Look in Add/Remove Programs or the program's About section for Update 12 (SE2024) or Update 3 (SE2025) mentions.
    Affected if The installed version lacks the V224.0 Update 12 or V225.0 Update 3 patches.

You are affected if Solid Edge SE2024 or SE2025 is installed with a version earlier than the respective Update 12 or Update 3 patches, or if Parasolid version falls within the vulnerable 36.1.x below 36.1.225 or 37.0.x below 37.0.173 ranges.

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 36.1.225 / 37.0.173 or later
Fixed in 36.1.22537.0.173
Interim mitigation

Update Solid Edge SE2024 to version V224.0 Update 12 or later, and SE2025 to V225.0 Update 3 or later. Until patched, avoid opening X_T files from untrusted sources and run the application with reduced privileges to limit impact of potential exploitation.

Recommended fix High confidence

Parasolid 36.1.225+ or 37.0.173+ | Solid Edge SE2024 V224.0 Update 12+ | Solid Edge SE2025 V225.0 Update 3+

  1. 1. Identify the currently installed Parasolid or Solid Edge version from the application's About/Help menu
  2. 2. For Parasolid users: If running version 36.1.x, upgrade to version 36.1.225 or later. If running version 37.0.x, upgrade to version 37.0.173 or later
  3. 3. For Solid Edge SE2024 users: Apply Update 12 (V224.0 Update 12) or later
  4. 4. For Solid Edge SE2025 users: Apply Update 3 (V225.0 Update 3) or later
  5. 5. Obtain the update from the official Siemens support portal (cert-portal.siemens.com) or through your software distribution channel
  6. 6. Before applying in production, test the updated version with your X_T workflow to verify compatibility
  7. 7. Apply the update and restart the application
Caveat Standard update - review release notes for any changes to X_T import behavior; test critical workflows before production deployment

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

Fix this in Parasolid 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-2024-54091 — 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-54091 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