CVE-2024-32061
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-21566)
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 specially crafted IGS (IGES) files. The vulnerability occurs when the application reads past the end of an allocated memory structure during file parsing, potentially allowing an attacker to achieve code execution in the context of the current process.
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 Siemens productCheck if Simcenter Femap or Siemens PS/IGES Parasolid Translator is installed by examining installed programs in Windows Settings > Apps & features, or checking the installation directory for femap.exe or parasolid_translator executablesAffected if Either Simcenter Femap or Siemens PS/IGES Parasolid Translator is present on the system
-
Determine Femap versionRight-click on the Femap application executable (femap.exe), select Properties, and view the Details tab for the Product Version fieldAffected if Product version is displayed and is below 2406.0000
-
Determine PS/IGES Parasolid Translator versionRight-click on the Parasolid Translator executable or check the application version through the Windows installed programs listAffected if Version is displayed and is below 27.1.215
-
Verify IGS file parsing capabilityConfirm the installation includes IGES/IGS file import functionality - this is a core file translator feature typically included by default in Femap and Parasolid Translator installationsAffected if The IGES file parsing module is loaded and accessible in the installed product
The environment is affected if either Simcenter Femap version < 2406.0000 or Siemens PS/IGES Parasolid Translator version < 27.1.215 is installed with the IGS file parsing capability available.
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 to Simcenter Femap version V2406 or later to remediate this vulnerability. Until the upgrade is applied, avoid opening untrusted IGS files from unknown or untrusted sources.
Simcenter Femap V2406.0000 (or later)
- 1. Identify the current version of Simcenter Femap by checking 'Help' > 'About' in the application
- 2. Download Simcenter Femap V2406.0000 or later from Siemens' official support portal (cert-portal.siemens.com)
- 3. Install the update following Siemens' standard installation procedure
- 4. Verify the upgrade was successful by checking the version shows V2406.0000 or higher
- 5. If using Ps/iges Parasolid Translator as a separate component, ensure it is also updated to version 27.1.215 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32061 — 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-32061 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