dbcve.org
Ps\/iges Parasolid TranslatorApplication · Siemens

CVE-2024-32060

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-21565)

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 an out-of-bounds read vulnerability in its IGS (IGES) file parser. When parsing specially crafted IGS files, the parser reads past the end of an allocated memory structure. This memory corruption can be leveraged by an attacker to achieve code execution in the context of the current process.

MitigationUpgrade to Simcenter Femap V2406 or later. Until then, exercise caution when 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 Simcenter Femap version
    Open Simcenter Femap, go to Help > About, or check the installation directory for version information. The executable is typically located in the Femap installation folder.
    Affected if The installed version is lower than 2406.0000
  2. Check Siemens Ps/iges Parasolid Translator version
    Locate the Ps/iges Parasolid Translator component in the installation directory or through Windows Programs and Features. Check the file version of the translator DLL or executable.
    Affected if The translator version is lower than 27.1.215
  3. Verify IGS import functionality is present
    Open Simcenter Femap and attempt to access the File > Import menu to confirm IGS/IGES file import capability exists and is enabled.
    Affected if IGS file import feature is available and the version is below 2406.0000 (Femap) or the translator is below 27.1.215
  4. Inspect IGES parser module
    Check the Simcenter Femap installation directory for IGES-related DLLs (typically named with 'igs' or 'iges' in the filename). Right-click on the DLL and view Properties > Details to confirm the file version.
    Affected if The IGES parser DLL version is not aligned with the patched version (27.1.215 or later for translator; 2406.0000 or later for Femap)

You are affected if Simcenter Femap is installed with a version below 2406.0000, or if the Ps/iges Parasolid Translator component is present and below version 27.1.215, and the IGS/IGES file import feature is enabled.

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 V2406 or later. Until then, exercise caution when opening IGS files from untrusted or unknown sources.

Recommended fix High confidence

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

  1. 1. Identify the installed product (Simcenter Femap or Ps/iges Parasolid Translator) and verify the current version.
  2. 2. Obtain the fixed version from the official Siemens support portal or authorized distribution channel.
  3. 3. For Simcenter Femap: Upgrade to version V2406.0000 or later.
  4. 4. For Ps/iges Parasolid Translator: Upgrade to version 27.1.215 or later.
  5. 5. After upgrading, validate that the software runs normally.
  6. 6. Apply least-privilege principles when processing untrusted IGS/IGES files in the updated software.

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

Fix this in Ps\/iges Parasolid Translator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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