dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39148

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

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, allowing arbitrary code execution in the current process context due to inadequate bounds checking during file parsing.

MitigationUpdate to vendor-patched versions (Parasolid V33.1.263, V34.0.252, V34.1.242, V35.0.164 or Femap V2022.1.3/V2022.2.2); avoid opening untrusted X_T files from unknown sources until patched.

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 Simcenter Femap version
    Open Femap, go to Help > About or check the installer/registry for version information (typically listed as 2022.1.x or 2022.2.x)
    Affected if Version is 2022.1 through 2022.1.2, or 2022.2 through 2022.2.1 (any version below 2022.1.3 or 2022.2.2 within the 2022.1 or 2022.2 branches)
  2. Identify installed Parasolid version
    Check the Parasolid component version via the hosting application's about/diagnostics, or locate the Parasolid DLL files (typically px_kernel.dll or similar) and inspect file properties for version info
    Affected if Version is 33.1.x below 33.1.263, 34.0.x below 34.0.252, 34.1.x below 34.1.242, or 35.0.x below 35.0.164
  3. Determine if X_T file parsing is used
    Inspect recent file open operations or look for X_T file handling capability in the software - check for presence of X_T files in recent document histories or file associations
    Affected if The software is configured to open or import X_T (Parasolid text) files from external sources

You are affected if you have Simcenter Femap versions 2022.1.x before 2022.1.3 or 2022.2.x before 2022.2.2, or Parasolid versions 33.1.x before 33.1.263, 34.0.x before 34.0.252, 34.1.x before 34.1.242, or 35.0.x before 35.0.164, and you parse X_T files with the vulnerable component.

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-patched versions (Parasolid V33.1.263, V34.0.252, V34.1.242, V35.0.164 or Femap V2022.1.3/V2022.2.2); avoid opening untrusted X_T files from unknown sources until patched.

Recommended fix High confidence

Simcenter Femap: V2022.1.3 or V2022.2.2 and later; Parasolid: V33.1.263, V34.0.252, V34.1.242, or V35.0.164 and later

  1. 1. Identify the currently installed version of Simcenter Femap or Parasolid by checking the application's 'About' or version information
  2. 2. For Simcenter Femap users: If running version 2022.1.x, upgrade to version 2022.1.3 or later; if running version 2022.2.x, upgrade to version 2022.2.2 or later
  3. 3. For Parasolid users: Upgrade to the minimum fixed version for your release line: V33.1.263 or later for V33.1; V34.0.252 or later for V34.0; V34.1.242 or later for V34.1; V35.0.164 or later for V35.0
  4. 4. Obtain the update from the official Siemens support portal or through your existing maintenance/contract channel
  5. 5. After upgrading, verify the new version is correctly installed
  6. 6. As a general precaution, only open X_T files from trusted sources until the update is applied
Caveat Upgrades within the same major version typically retain compatibility; verify with release notes if there are any model format changes

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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