dbcve.org
ParasolidApplication · Siemens

CVE-2023-41032

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 34.1.258 / 35.0.253 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 Parasolid V34.1 (All versions < V34.1.258), Parasolid V35.0 (All versions < V35.0.253), Parasolid V35.1 (All versions < V35.1.184), Parasolid V36.0 (All versions < V36.0.142), Simcenter Femap V2301 (All versions < V2301.0003), Simcenter Femap V2306 (All versions < V2306.0001). The affected application contains an out of bounds write past the end of an allocated structure while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21263)

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 Parasolid and Simcenter Femap's X_T file parser where an out-of-bounds write occurs past the end of an allocated structure when parsing specially crafted files. This can be leveraged by an attacker to achieve code execution in the context of the current process.

MitigationUpdate to the patched versions (Parasolid V34.1.258, V35.0.253, V35.1.184, V36.0.142; Simcenter Femap V2301.0003, V2306.0001) or exercise extreme caution when opening untrusted X_T 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
ParasolidApplication
Affected:>= 34.1, < 34.1.258>= 35.0, < 35.0.253>= 35.1, < 35.1.184>= 36.0, < 36.0.142
Simcenter FemapApplication
Affected:>= 2301.0, < 2301.0003>= 2306.0, < 2306.0001

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 if Siemens Parasolid is installed
    Check for Parasolid installation directory (commonly under Program Files/Siemens) or search for parasolid.exe in common installation paths. Use 'Get-ChildItem -Path 'C:\Program Files' -Recurse -Filter 'parasolid*' -ErrorAction SilentlyContinue' on Windows or 'find /usr -name '*parasolid*' 2>/dev/null' on Linux.
    Affected if Parasolid is found and its version falls within: >=34.1 to <34.1.258, >=35.0 to <35.0.253, >=35.1 to <35.1.184, or >=36.0 to <36.0.142
  2. Identify if Siemens Simcenter Femap is installed
    Check for Simcenter Femap installation (typically under Program Files/Siemens/Femap or similar). Search for femap.exe or check Add/Remove Programs for Siemens Simcenter Femap entry.
    Affected if Simcenter Femap is found and its version falls within: >=2301.0 to <2301.0003 or >=2306.0 to <2306.0001
  3. Determine the exact Parasolid version
    Run parasolid with version flag, check the product About dialog, or locate the version in the installation directory metadata. Compare your version number against the affected ranges listed in the CVE.
    Affected if The installed Parasolid version is less than 34.1.258, 35.0.253, 35.1.184, or 36.0.142 (depending on your release branch)
  4. Determine the exact Simcenter Femap version
    Open Femap and go to Help > About, or check the application entry in Add/Remove Programs. Compare the version number against the affected ranges.
    Affected if The installed Femap version is less than 2301.0003 or 2306.0001

You are affected if Siemens Parasolid or Simcenter Femap is installed with a version matching the affected ranges and you process X_T 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 34.1.258 / 35.0.253 / 35.1.184 or later
Fixed in 34.1.25835.0.25335.1.184
Interim mitigation

Update to the patched versions (Parasolid V34.1.258, V35.0.253, V35.1.184, V36.0.142; Simcenter Femap V2301.0003, V2306.0001) or exercise extreme caution when opening untrusted X_T files from unknown sources.

Recommended fix High confidence

Parasolid: V34.1.258, V35.0.253, V35.1.184, or V36.0.142 (depending on your product line); Simcenter Femap: V2301.0003 or V2306.0001 (depending on your version)

  1. 1. Identify the installed Parasolid or Simcenter Femap version by checking the application's 'About' or version information.
  2. 2. For Parasolid users: Determine if your version is in the affected range (34.1 through 34.1.257, 35.0 through 35.0.252, 35.1 through 35.1.183, or 36.0 through 36.0.141).
  3. 3. For Simcenter Femap users: Determine if your version is in the affected range (2301.0 through 2301.0002 or 2306.0 through 2306.0000).
  4. 4. Obtain the fixed version from Siemens PLM Software (for Parasolid) or Siemens Digital Industries Software (for Simcenter Femap) via their support portal or update mechanism.
  5. 5. Apply the update: For Parasolid V34.1.x, upgrade to V34.1.258 or later; For Parasolid V35.0.x, upgrade to V35.0.253 or later; For Parasolid V35.1.x, upgrade to V35.1.184 or later; For Parasolid V36.0.x, upgrade to V36.0.142 or later.
  6. 6. For Simcenter Femap V2301.x, upgrade to V2301.0003 or later; For Simcenter Femap V2306.x, upgrade to V2306.0001 or later.
  7. 7. Verify the update was successful by checking the version information again.
  8. 8. As a temporary mitigation, avoid opening untrusted X_T files from unknown or untrusted sources.

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

Fix this in Parasolid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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