dbcve.org
Simcenter FemapApplication · Siemens

CVE-2024-24923

HIGH · 7.8 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 2306.0001 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), Simcenter Femap (All versions < V2306.0001). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted Catia MODEL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-22055)

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 · moderate confidence

Simcenter Femap contains an out-of-bounds read vulnerability when parsing Catia MODEL files. The parser reads past the end of an allocated structure due to insufficient bounds checking, potentially allowing an attacker to achieve code execution in the context of the current process.

MitigationUpdate to version V2401.0000 or V2306.0001 or later to patch the vulnerability. 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:< 2306.0001

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 if Simcenter Femap is installed
    Look for Simcenter Femap in the Windows Start Menu, Program Files directory, or check for femap.exe in common installation paths (e.g., C:\Program Files\Siemens\Femap). On Linux, check /opt/siemens/femap or equivalent.
    Affected if Femap is not installed on the system - not applicable
  2. Determine installed Femap version
    In Femap, go to Help > About Femap or look for version information in the executable properties (right-click femap.exe > Properties > Details). Alternatively, check the installation directory for version documentation.
    Affected if Version is lower than 2306.0001 (e.g., 2306, 2303, etc.) - vulnerable
  3. Check for recent Catia MODEL file usage
    Review recent file access logs, Windows Event Viewer for file open events, or check the application's recent files list (File > Recent) for .model files from Catia.
    Affected if Catia MODEL files have been opened in the affected version - potentially exploited or at risk
  4. Inspect Femap installation for Catia import modules
    Check the Femap installation directory (e.g., C:\Program Files\Siemens\Femap\) for DLLs related to Catia import (look for files containing 'catia', 'cat', or 'model' in filenames).
    Affected if Catia import functionality is present in the installation - the vulnerable parser exists

If Simcenter Femap version is lower than 2306.0001 and the Catia MODEL file parser is present, the environment is vulnerable to out-of-bounds read exploitation.

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 2306.0001 or later
Fixed in 2306.0001
Interim mitigation

Update to version V2401.0000 or V2306.0001 or later to patch the vulnerability. Until patched, avoid opening Catia MODEL files from untrusted sources.

Recommended fix High confidence

Simcenter Femap V2306.0001 or later (V2401.0000 recommended)

  1. 1. Identify the current installed version of Simcenter Femap by checking 'Help' > 'About Simcenter Femap' in the application
  2. 2. Navigate to the Siemens Support portal at https://support.sw.siemens.com/ or contact your Siemens representative to obtain the upgrade package
  3. 3. Download Simcenter Femap V2306.0001 or later (V2401.0000 recommended for most recent fixes)
  4. 4. Before upgrading, back up all custom templates, configurations, and any existing Femap model files (.fem, .cdb, etc.)
  5. 5. Close all running instances of Simcenter Femap
  6. 6. Run the installer with administrator privileges and follow the installation wizard prompts
  7. 7. After installation, verify the new version by checking 'Help' > 'About Simcenter Femap' confirms V2306.0001 or later
  8. 8. Test critical workflows with existing Catia MODEL file imports to confirm functionality
Caveat Review Siemens release notes for V2306.0001 and V2401.0000 for any deprecated features or workflow changes; custom macros and scripts may require revalidation after upgrade

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

Fix this in Simcenter Femap Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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