dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39139

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

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 a buffer overflow in Parasolid and Simcenter Femap when parsing X_T files. The application writes past the end of an allocated buffer during parsing of specially crafted files, allowing arbitrary code execution in the context of the current process.

MitigationUpdate to the vendor-supplied patched versions (V33.1.262, V34.0.252, V34.1.242, V35.0.161, V2022.1.3, V2022.2.2 or later). Avoid opening untrusted X_T files until patches are applied.

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. Check Simcenter Femap version
    Open Femap and go to Help > About, or check the installed programs list in Windows Control Panel. Note the full version number (e.g., 2022.1.0, 2022.2.1)
    Affected if Version is 2022.1.x where x < 3, OR version is 2022.2.x where x < 2 (for example, 2022.1.0 through 2022.1.2, or 2022.2.0 through 2022.2.1)
  2. Check Parasolid version
    Parasolid version can be found in the software that bundles it (such as Siemens NX, Solid Edge, or Femap). Check the Parasolid version info in the application's About or license information, or look for Parasolid version in Windows Registry under HKLM\Software\UGS\Parasolid
    Affected if Version is 33.1.x where x < 262, OR 34.0.x where x < 252, OR 34.1.x where x < 242, OR 35.0.x where x < 161 (for example, 33.1.100 through 33.1.261)
  3. Verify X_T file handling is in use
    Check if the system or associated CAD/CAE applications regularly import or open .x_t (Parasolid tessellated) files. This is the attack vector for this buffer overflow
    Affected if The software is used to open X_T files from external or untrusted sources

You are affected if either Simcenter Femap or Parasolid is installed at a version within the vulnerable ranges AND the software is used to parse X_T files from potentially untrusted sources.

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 vendor-supplied patched versions (V33.1.262, V34.0.252, V34.1.242, V35.0.161, V2022.1.3, V2022.2.2 or later). Avoid opening untrusted X_T files until patches are applied.

Recommended fix High confidence

Simcenter Femap: upgrade to V2022.1.3 or V2022.2.2 | Parasolid: upgrade to V33.1.262, V34.0.252, V34.1.242, or V35.0.161 depending on your major version

  1. Obtain the fixed version of Simcenter Femap (V2022.1.3 or V2022.2.2) from the Siemens support portal or authorized distribution channel
  2. Obtain the fixed version of Parasolid corresponding to your major version: V33.1.262, V34.0.252, V34.1.242, or V35.0.161 from Siemens
  3. Ensure all instances of the affected software are closed before applying the update
  4. Install the updated version following standard Siemens installation procedures
  5. Restart the application after installation completes
  6. Verify the installed version matches the fixed release (2022.1.3 or higher for Femap 2022.1; 2022.2.2 or higher for Femap 2022.2; or respective Parasolid versions)
Caveat Review Siemens release notes for any behavioral changes or deprecated features between your current version and the fixed release

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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