dbcve.org
Ps\/iges Parasolid TranslatorApplication · Siemens

CVE-2024-32063

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 27.1.215 / 2406.0000 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 Simcenter Femap (All versions < V2406). The affected application contains a type confusion vulnerability while parsing IGS files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21573)

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

Simcenter Femap contains a type confusion vulnerability in its IGS (IGES) file parsing logic. An attacker can exploit this by crafting a malicious IGS file that triggers the type confusion, allowing arbitrary code execution within the context of the running application process.

MitigationUpdate Simcenter Femap to version V2406 or later to obtain the vendor patch for this vulnerability.

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
Ps\/iges Parasolid TranslatorApplication
Affected:< 27.1.215
Simcenter FemapApplication
Affected:< 2406.0000

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. Determine installed Simcenter Femap version
    Open Simcenter Femap and navigate to Help > About, or check the application's version information in the installation directory. Alternatively, locate the executable file (femap.exe) and view its properties to find the version number.
    Affected if The installed version is lower than 2406.0000 (for example, V2401, V2312, etc.)
  2. Determine installed Ps/iges Parasolid Translator version
    Check the version of the Siemens Ps/iges Parasolid Translator component if installed as a separate module. This is typically found in the translator's own about or version information, or within the Siemens installation management tool.
    Affected if The translator version is lower than 27.1.215
  3. Verify IGS/IGES file import capability is in use
    Confirm whether your workflow involves importing or opening IGES (.igs, .iges) files within Simcenter Femap. Check recent file history or look for IGS-related import options in the File > Import menu.
    Affected if You regularly import or open IGES files using Simcenter Femap, making the parsing logic active in your environment
  4. Compare installed versions against CVE-affected ranges
    Document both the Simcenter Femap version (must be < 2406.0000) and the Ps/iges Parasolid Translator version (must be < 27.1.215). If either component falls within the affected version range and IGS file processing is used, your environment is potentially vulnerable.
    Affected if Either component version is below the safe threshold AND IGES file parsing is enabled

Your environment is affected if Simcenter Femap is installed at a version below 2406.0000 or the Ps/iges Parasolid Translator is below 27.1.215, and you use IGES file import functionality.

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 27.1.215 / 2406.0000 or later
Fixed in 27.1.2152406.0000
Interim mitigation

Update Simcenter Femap to version V2406 or later to obtain the vendor patch for this vulnerability.

Recommended fix High confidence

Simcenter Femap V2406.0000 (or later) / Ps/iges Parasolid Translator 27.1.215

  1. Obtain Simcenter Femap V2406.0000 or later from the official Siemens support portal (cert-portal.siemens.com or siemens.com/support)
  2. Download the updated Simcenter Femap installation package
  3. Close all running instances of Simcenter Femap
  4. Run the installer and follow the prompts to upgrade to V2406.0000
  5. Verify the installation by checking Help > About to confirm the version number

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

Fix this in Ps\/iges Parasolid Translator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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