dbcve.org
Simcenter FemapApplication · Siemens

CVE-2024-24921

HIGH · 7.8 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 2401.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 < V2401.0000). The affected application is vulnerable to memory corruption while parsing specially crafted Catia MODEL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21712)

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 Catia MODEL files. An attacker can trigger this by convincing a user to open a malicious Catia MODEL file, potentially executing arbitrary code in the context of the current process.

MitigationUpdate Simcenter Femap to version V2401.0000 or later. Until patched, avoid opening Catia MODEL files from untrusted 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
Simcenter FemapApplication
Affected:< 2401.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. Confirm Simcenter Femap is installed
    Check for Simcenter Femap in the Windows installed programs list (Control Panel > Programs and Features) or look for the installation directory, typically under C:\Program Files\Siemens\ or C:\Program Files (x86)\Siemens\
    Affected if Simcenter Femap is present on the system
  2. Determine installed Femap version
    Open Femap and navigate to Help > About Simcenter Femap, or check the executable properties (right-click femap.exe > Properties > Details) to find the File Version
    Affected if Version number is lower than 2401.0000 (e.g., 2301.x, 2201.x, etc.)
  3. Verify Catia import capability is present
    Check if the Catia MODEL import functionality is available in Femap: try File > Import > CATIA, or look for Catia-related menu options or add-on modules
    Affected if Catia MODEL import feature is present and enabled in the installation
  4. Audit recent Catia MODEL file access
    Review Windows recent documents, Femap's recent files list, or check file system audit logs for any recently opened .model files from the Catia import feature
    Affected if User has opened Catia MODEL files from potentially untrusted sources recently

You are affected if Simcenter Femap is installed with a version lower than 2401.0000 AND the Catia MODEL import feature is available or has been used to open 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 2401.0000 or later
Fixed in 2401.0000
Interim mitigation

Update Simcenter Femap to version V2401.0000 or later. Until patched, avoid opening Catia MODEL files from untrusted sources.

Recommended fix High confidence

V2401.0000 (or any version >= 2401.0000)

  1. Identify the current installed version of Simcenter Femap
  2. Obtain Simcenter Femap V2401.0000 or later from the official Siemens download portal (cert-portal.siemens.com or siemens.com/support)
  3. Create a backup of all existing Femap projects, templates, and user settings
  4. Uninstall the current version of Simcenter Femap or use the upgrade installer option
  5. Install Simcenter Femap V2401.0000 following the Siemens installation documentation
  6. Launch the application and verify successful startup
  7. Test parsing of Catia MODEL files to confirm the vulnerability is addressed

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

Fix this in Simcenter Femap 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-24921 — 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-24921 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