dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39138

HIGH · 7.8 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to 33.1.262 / 34.0.252 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 Parasolid V33.1 (All versions < V33.1.262), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.161), Simcenter Femap V2022.1 (All versions < V2022.1.3), Simcenter Femap V2022.2 (All versions < V2022.2.2). The affected application contains an out of bounds write past the end of an allocated buffer while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-17284)

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

The vulnerability is an out-of-bounds write past the end of an allocated buffer in the X_T file parser of Parasolid and Simcenter Femap. Specially crafted X_T files can trigger this memory corruption, potentially allowing arbitrary code execution in the context of the current process.

MitigationUpdate to the fixed versions: Parasolid V33.1.262, V34.0.252, V34.1.242, V35.0.161, Simcenter Femap V2022.1.3, V2022.2.2. Until updated, avoid opening untrusted X_T files from unknown or 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:>= 2022.1, < 2022.1.3>= 2022.2, < 2022.2.2
ParasolidApplication
Affected:>= 33.1, < 33.1.262>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.161

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. Identify Simcenter Femap installation and version
    Check for Simcenter Femap installation directory (typically under Program Files/Siemens) and locate the version information in the application or release notes. Common paths: C:\Program Files\Siemens\Femap2022\ or check the About dialog in the application.
    Affected if Version is >= 2022.1 and < 2022.1.3, OR >= 2022.2 and < 2022.2.2
  2. Identify Parasolid installation and version
    Parasolid is typically embedded in Siemens NX, Simcenter, or other CAD applications. Check the Parasolid version through the host application's help/about dialog, or look for psolver.exe and check its version property.
    Affected if Version is >= 33.1 and < 33.1.262, OR >= 34.0 and < 34.0.252, OR >= 34.1 and < 34.1.242, OR >= 35.0 and < 35.0.161
  3. Verify X_T file handling capability
    The vulnerability exists in the X_T file parser module. Confirm whether the installed software has X_T import functionality enabled (this is typically a built-in feature in both Femap and Parasolid-based applications).
    Affected if The software includes X_T file import capability and a vulnerable version is installed

You are affected if either Simcenter Femap or a Parasolid-based application with a vulnerable version is installed AND the software can import X_T 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 33.1.262 / 34.0.252 / 34.1.242 or later
Fixed in 33.1.26234.0.25234.1.242
Interim mitigation

Update to the fixed versions: Parasolid V33.1.262, V34.0.252, V34.1.242, V35.0.161, Simcenter Femap V2022.1.3, V2022.2.2. Until updated, avoid opening untrusted X_T files from unknown or untrusted sources.

Recommended fix High confidence

Simcenter Femap V2022.1.3 or V2022.2.2 (or later); Parasolid V33.1.262, V34.0.252, V34.1.242, V35.0.161, or later

  1. 1. Identify the installed version of Simcenter Femap or Parasolid by checking the application's About/Help section
  2. 2. For Simcenter Femap: If version is 2022.1.x where x < 3, or 2022.2.x where x < 2, an upgrade is required
  3. 3. For Parasolid: If version is 33.1.x where x < 262, 34.0.x where x < 252, 34.1.x where x < 242, or 35.0.x where x < 161, an upgrade is required
  4. 4. Obtain the fixed version from the official Siemens support portal or your existing license/distribution channel
  5. 5. Download the appropriate fixed version (Femap V2022.1.3 or V2022.2.2, or Parasolid V33.1.262/V34.0.252/V34.1.242/V35.0.161 or later)
  6. 6. Backup all important data and project files before proceeding
  7. 7. Uninstall the current version or apply the update following Siemens installation documentation
  8. 8. Verify the installed version matches the fixed release after installation
Caveat Minor - this is a patch release addressing security; verify any custom workflows or plugins remain compatible

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

Fix this in Simcenter Femap Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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