dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39146

HIGH · 7.8 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to 33.1.263 / 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 V33.1 (All versions >= V33.1.262 < V33.1.263), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.161), Parasolid V35.0 (All versions >= V35.0.161 < V35.0.164), Simcenter Femap V2022.1 (All versions < V2022.1.3), Simcenter Femap V2022.2 (All versions < V2022.2.2). The affected application is vulnerable to uninitialized pointer access while parsing specially crafted X_T files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-17502)

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 exists in Parasolid and Simcenter Femap when parsing X_T files. A specially crafted X_T file causes an uninitialized pointer to be accessed during parsing, leading to arbitrary code execution in the context of the current process. This is a memory corruption vulnerability in the file format parser.

MitigationApply vendor-provided patches to update to the fixed versions (V33.1.263, V34.0.252, V34.1.242, V35.0.164, V2022.1.3, V2022.2.2) or later. Until patches are applied, avoid opening untrusted X_T 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
Simcenter FemapApplication
Affected:>= 2022.1, < 2022.1.3>= 2022.2, < 2022.2.2
ParasolidApplication
Affected:>= 33.1, < 33.1.263>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.164

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 installed Siemens products
    Check if Siemens Parasolid or Simcenter Femap is installed on the system. This may be as a standalone application, CAD integration, or embedded in other Siemens software (such as NX, Solid Edge, or Teamcenter).
    Affected if Either Parasolid or Simcenter Femap is present on the system.
  2. Determine Simcenter Femap version
    Open Simcenter Femap and navigate to Help > About Femap (or equivalent version info dialog) to view the installed version number.
    Affected if The installed version is 2022.1.x where x < 3, or 2022.2.x where x < 2.
  3. Determine Parasolid version
    Check the Parasolid version through the host application (if integrated) or look for version information in the Siemens software licensing or installation details. Parasolid version typically appears as V33.1.x, V34.0.x, V34.1.x, or V35.0.x.
    Affected if The installed version is 33.1.x where x < 263, 34.0.x where x < 252, 34.1.x where x < 242, or 35.0.x where x < 164.
  4. Confirm X_T file parsing is in use
    Determine whether the installation has been used to import or open X_T (Parasolid Text) files. This may be evident from recent file history, user workflows, or CAD data exchange processes.
    Affected if X_T file import functionality is available or has been used, as the vulnerability triggers specifically when parsing X_T files.

You are affected if Simcenter Femap version is below 2022.1.3 or below 2022.2.2, OR Parasolid version is below 33.1.263, 34.0.252, 34.1.242, or 35.0.164, AND the software is used to parse 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.263 / 34.0.252 / 34.1.242 or later
Fixed in 33.1.26334.0.25234.1.242
Interim mitigation

Apply vendor-provided patches to update to the fixed versions (V33.1.263, V34.0.252, V34.1.242, V35.0.164, V2022.1.3, V2022.2.2) or later. Until patches are applied, avoid opening untrusted X_T files from unknown sources.

Recommended fix High confidence

Simcenter Femap: 2022.1.3 or 2022.2.2+ | Parasolid: V33.1.263, V34.0.252, V34.1.242, or V35.0.164+

  1. 1. Identify the exact version of Simcenter Femap currently installed.
  2. 2. If using Simcenter Femap V2022.1.x, upgrade to version 2022.1.3 or later.
  3. 3. If using Simcenter Femap V2022.2.x, upgrade to version 2022.2.2 or later.
  4. 4. For Parasolid (if used as a standalone component), upgrade to the appropriate fixed version: V33.1.263, V34.0.252, V34.1.242, or V35.0.164 (or later).

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

Fix this in Simcenter Femap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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