dbcve.org
Ps\/iges Parasolid TranslatorApplication · Siemens

CVE-2024-32065

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 applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted IGS files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21577)

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 · moderate confidence

Simcenter Femap contains an out-of-bounds read vulnerability in its IGS (IGES) file parser. When parsing specially crafted IGS 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.

MitigationUpgrade to Simcenter Femap version V2406 or later. Until upgraded, avoid opening IGS files from untrusted or 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
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. Check if Simcenter Femap is installed
    Look for Simcenter Femap in the Windows Start Menu, Program Files, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Femap for the installation path
    Affected if Femap is present on the system
  2. Determine the installed Femap version
    Open Femap and go to Help > About, or check the version in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Femap\ProductVersion
    Affected if The version number is lower than 2406.0000 (for example, 2403.0000 or earlier)
  3. Check if Siemens PS/iges Parasolid Translator is installed
    Search for PS/iges in Program Files or check for the ParasolidTranslator IGES component in the Windows registry
    Affected if The PS/iges Parasolid Translator component is present
  4. Determine the PS/iges Parasolid Translator version
    Check the file version of psiges.dll in the installation directory, or look for version information in the Windows registry under the Parasolid translator keys
    Affected if The version is lower than 27.1.215 or the version cannot be determined (implying an older release)
  5. Verify IGS file parsing capability is accessible
    Attempt to import an .igs or .iges file in Femap via File > Import, or check if the IGES translator is listed as an available import option
    Affected if The IGS/IGES import feature is available and the installed version is below the fixed release

You are affected if Simcenter Femap below version 2406.0000 or PS/iges Parasolid Translator below version 27.1.215 is installed AND the IGS/IGES file import functionality can be accessed.

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

Upgrade to Simcenter Femap version V2406 or later. Until upgraded, avoid opening IGS files from untrusted or unknown sources.

Recommended fix High confidence

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

  1. 1. Back up all existing Simcenter Femap data and configuration files
  2. 2. Uninstall the current version of Simcenter Femap if upgrading from a very old release
  3. 3. Download Simcenter Femap V2406.0000 or later from the Siemens Support portal (support.industrysoftware.siemens.com)
  4. 4. Run the installer with administrative privileges
  5. 5. During installation, choose the appropriate installation type (typical/custom) for your environment
  6. 6. After installation, verify the version by checking Help > About Simcenter Femap
  7. 7. Re-apply any custom configurations or templates from the backup
  8. 8. Test critical IGS file parsing workflows to confirm functionality

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

Fix this in Ps\/iges Parasolid Translator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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