dbcve.org
Ps\/iges Parasolid TranslatorApplication · Siemens

CVE-2024-32058

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 is vulnerable to memory corruption while parsing specially crafted IGS files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21563)

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 memory corruption vulnerability when parsing specially crafted IGS (IGES) files. This allows an attacker to potentially execute arbitrary code in the context of the current process by tricking a user into opening a malicious IGS file.

MitigationUpgrade to Simcenter Femap version V2406 or later to remediate this vulnerability. Avoid opening untrusted IGS files from 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 installed version
    Open Simcenter Femap, then navigate to Help > About to view the exact version number. Alternatively, check the program files directory or Windows Add/Remove Programs for the installed version.
    Affected if The version displayed is below 2406.0000 (e.g., 2403.x, 2312.x, etc.)
  2. Check Siemens PS/IGES Parasolid Translator version
    Within Simcenter Femap, access the translator or import settings, or check the installed Parasolid components via Windows Programs and Features. The PS/IGES translator is typically bundled with Femap.
    Affected if The PS/IGES Parasolid Translator version is below 27.1.215
  3. Identify IGS file processing usage
    Review recent file import history or check if IGS (IGES) file imports are commonly performed in the Femap workflow. Look for .igs or .iges file extensions in recent project directories.
    Affected if IGS files have been opened or imported into Femap recently, especially from untrusted sources
  4. Verify IGS import capability is enabled
    Check Femap file import options (File > Import) to confirm IGES/IGS import translator is available and not disabled.
    Affected if The IGES import option is present and functional in the Femap installation

You are affected if Simcenter Femap version is below 2406.0000 or the PS/IGES Parasolid Translator is below 27.1.215, and you process IGS/IGES files.

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 to remediate this vulnerability. Avoid opening untrusted IGS files from unknown sources.

Recommended fix High confidence

Simcenter Femap V2406 (2406.0000)

  1. 1. Identify the current version of Simcenter Femap installed on the system
  2. 2. Download Simcenter Femap V2406 (or later) from the official Siemens Support Portal (support.industrysoftware.siemens.com)
  3. 3. Ensure all work data and project files are backed up before upgrading
  4. 4. Run the installer for Simcenter Femap V2406
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. Verify the installed version shows V2406.0000 or later after installation

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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