dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39150

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

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

Out-of-bounds write vulnerability in Parasolid and Simcenter Femap when parsing specially crafted X_T files. The application writes past the end of an allocated buffer during X_T file parsing, potentially allowing an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate to vendor-provided patched 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. Avoid opening untrusted X_T files from untrusted sources 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.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. Compare the version number to the affected ranges: 2022.1.x where x < 3, or 2022.2.x where x < 2
    Affected if The installed version is 2022.1.0 through 2022.1.2, or 2022.2.0 through 2022.2.1
  2. Check Parasolid library version
    If you have an application that embeds Parasolid, check the Parasolid library version file or the application About dialog which often lists included component versions. Compare against affected ranges: 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
    Affected if The Parasolid library version falls within any of these vulnerable ranges: 33.1.0-33.1.262, 34.0.0-34.0.251, 34.1.0-34.1.241, or 35.0.0-35.0.163
  3. Determine X_T file parsing usage
    Identify if your workflow involves opening or importing X_T (Parasolid Text) files in the affected software. Check recent file history or document templates for .x_t file extensions
    Affected if The software is used to open X_T files from untrusted or external sources

You are affected if the installed Simcenter Femap or Parasolid version falls within the vulnerable version ranges AND you process X_T files with the application.

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

Update to vendor-provided patched 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. Avoid opening untrusted X_T files from untrusted sources until patches are applied.

Recommended fix High confidence

Simcenter Femap 2022.1.3 or later / 2022.2.2 or later; Parasolid 33.1.263 / 34.0.252 / 34.1.242 / 35.0.164 or later

  1. 1. Identify the exact version of Simcenter Femap or Parasolid currently installed.
  2. 2. For Simcenter Femap: If running version 2022.1.x where x < 3, upgrade to version 2022.1.3 or later.
  3. 3. For Simcenter Femap: If running version 2022.2.x where x < 2, upgrade to version 2022.2.2 or later.
  4. 4. For Parasolid V33.1.x: Upgrade to version 33.1.263 or later.
  5. 5. For Parasolid V34.0.x: Upgrade to version 34.0.252 or later.
  6. 6. For Parasolid V34.1.x: Upgrade to version 34.1.242 or later.
  7. 7. For Parasolid V35.0.x: Upgrade to version 35.0.164 or later.
  8. 8. Obtain upgrades from the official Siemens support portal or through your existing licensing channel.
Caveat Major version upgrades may introduce changes to file formats or features; review release notes before upgrading in production environments

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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