dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39143

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

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

A stack-based buffer overflow vulnerability exists in Parasolid and Simcenter Femap when parsing X_T CAD files. The application writes past the end of an allocated buffer during X_T file parsing, which can be triggered by a specially crafted malicious file and potentially allow arbitrary code execution in the current process context.

MitigationApply vendor-provided patches to reach safe versions: Parasolid V33.1.263, V34.0.252, V34.1.242, V35.0.164 or later; Simcenter Femap 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. Check Simcenter Femap version
    Open Femap, go to Help > About, or check the installation directory for version information. Look for the exact version number (e.g., 2022.1.0, 2022.1.2, 2022.2.0, 2022.2.1).
    Affected if The installed version is 2022.1.0 through 2022.1.2, or 2022.2.0 through 2022.2.1 (any version >= 2022.1 but < 2022.1.3, or >= 2022.2 but < 2022.2.2).
  2. Check Parasolid component version
    If Parasolid is installed as a standalone component or SDK, check the Parasolid version through the installation, or inspect any version file/dll properties in the Parasolid bin directory.
    Affected if The installed Parasolid version falls in these ranges: >= 33.1 but < 33.1.263, >= 34.0 but < 34.0.252, >= 34.1 but < 34.1.242, or >= 35.0 but < 35.0.164.
  3. Determine X_T file parsing usage
    Identify whether your workflows involve opening X_T (Parasolid Text) CAD files in the affected software. Check recent file history or document templates for .x_t file extensions.
    Affected if X_T CAD file parsing is enabled and you open files from potentially untrusted sources.

You are affected if either Simcenter Femap or Parasolid is installed with a version matching the affected ranges AND X_T file parsing is used in your environment.

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 reach safe versions: Parasolid V33.1.263, V34.0.252, V34.1.242, V35.0.164 or later; Simcenter Femap 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 to V2022.1.3 or V2022.2.2; Parasolid to V33.1.263, V34.0.252, V34.1.242, or V35.0.164

  1. Identify the currently installed version of Simcenter Femap or Parasolid by checking the application's 'About' or version information
  2. For Simcenter Femap: If version is >=2022.1 and <2022.1.3, upgrade to version 2022.1.3 or later
  3. For Simcenter Femap: If version is >=2022.2 and <2022.2.2, upgrade to version 2022.2.2 or later
  4. For Parasolid V33.1: Upgrade to version 33.1.263 or later
  5. For Parasolid V34.0: Upgrade to version 34.0.252 or later
  6. For Parasolid V34.1: Upgrade to version 34.1.242 or later
  7. For Parasolid V35.0: Upgrade to version 35.0.164 or later
  8. After upgrading, validate that the X_T file parser functions correctly with legitimate files

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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