CVE-2024-32066
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 · uneditedA 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-21578)
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 confidenceSimcenter Femap contains an out-of-bounds read vulnerability when parsing IGS (IGES) files. The parser reads past the end of an allocated memory structure, which can corrupt memory and potentially allow an attacker to execute arbitrary code in the context of the current process by tricking a user into opening a specially crafted malicious IGS file.
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< 27.1.215< 2406.0000CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Simcenter Femap versionOpen Simcenter Femap and go to Help > About, or check the installation directory for version information. On Windows, common paths are C:\Program Files\Siemens\Femap or C:\Program Files (x86)\Siemens\Femap. Look for executable or DLL files with version properties, or check the uninstall registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Femap entries.Affected if The installed version is lower than 2406.0000 (for example, 2403.x, 2306.x, or earlier releases).
-
Identify installed Ps/iges Parasolid Translator versionCheck the Parasolid translator installation. On Windows, look in C:\Program Files\Siemens\Parasolid or C:\Program Files (x86)\Siemens\Parasolid. Locate the psiges.dll or related translator components and inspect their file properties for version information. Also check Add/Remove Programs or the Windows registry for Siemens Parasolid entries.Affected if The translator version is lower than 27.1.215.
-
Determine if IGS file parsing is used or accessibleVerify whether the Femap installation includes IGS (IGES) import functionality. Check for the presence of IGS-related modules, plugins, or import filters in the Femap installation directory. Look for files with igs, iges, or translator in their names within the program folders.Affected if IGS file import capability is present in the installation and users have access to the File > Import function with IGES/IGS options.
-
Check for recent IGS file processing activityReview recent import operations or file access logs if available. In Femap, check recent session files or examine the application's file history. On Windows, review the Prefetch folder or temp directories for recently opened IGS files. Also check Windows Event Viewer for application errors related to IGES parsing.Affected if IGS files have been opened or imported into the affected Femap version.
You are affected if either Simcenter Femap version is below 2406.0000 or the Ps/iges Parasolid Translator version is below 27.1.215, AND the IGS file parsing feature is available or has been used to open files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped27.1.2152406.0000
Upgrade Simcenter Femap to version V2406 or later to patch the vulnerability. Until upgraded, avoid opening untrusted or unknown IGS files from unverified sources.
Simcenter Femap V2406.0000 and PS/IGES Parasolid Translator 27.1.215
- Identify the exact installed version of Simcenter Femap or PS/IGES Parasolid Translator
- Download Simcenter Femap V2406.0000 or later from the Siemens support portal
- Download PS/IGES Parasolid Translator version 27.1.215 or later from the Siemens support portal
- Back up all existing Femap project files and configurations
- Install the updated Simcenter Femap version by running the installer with administrative privileges
- If using PS/IGES Parasolid Translator separately, install the updated version 27.1.215
- Restart the system after installation completes
- Verify the installed version matches the fixed release (V2406.0000 for Femap, 27.1.215 for Parasolid Translator)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32066 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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