dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39145

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 out of bounds read past the end of an allocated buffer when parsing X_T files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-17496)

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

Parasolid and Simcenter Femap contain an out-of-bounds read vulnerability when parsing X_T CAD files. The application reads past the end of an allocated buffer, which can be exploited to execute arbitrary code in the context of the current process.

MitigationUpdate to the patched versions: Parasolid V33.1.263+, V34.0.252+, V34.1.242+, V35.0.164+; Simcenter Femap V2022.1.3+, V2022.2.2+. Until patched, avoid opening untrusted X_T files.

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 product
    Check for Simcenter Femap or Parasolid installation. On Windows, look in Program Files for 'Siemens' folder or check installed programs. For Parasolid, it may be embedded in other Siemens CAD products (NX, Solid Edge).
    Affected if Either Simcenter Femap or any Parasolid-based product is installed
  2. Determine Simcenter Femap version
    Open Femap, go to Help > About or check the executable properties (right-click femap.exe > Properties > Details). Alternatively, check the installation directory for version info.
    Affected if Version is 2022.1.x where x < 3, or 2022.2.x where x < 2
  3. Determine Parasolid version
    For Parasolid as a standalone: check the Parasolid installation folder for version information. For Parasolid embedded in other Siemens products (NX, Solid Edge): open the application's About dialog or check the product's version information. Parasolid version can sometimes be found in log files or the application's license/About information.
    Affected if Version is 33.1.x where x < 263, or 34.0.x where x < 252, or 34.1.x where x < 242, or 35.0.x where x < 164
  4. Verify X_T CAD file parsing capability
    Confirm the installation includes X_T file import functionality. Check if the application has X_T/X_B file import options available in the file open dialog.
    Affected if The product has X_T file parsing enabled or available as an import option

The environment is affected if Simcenter Femap (any version between 2022.1.0-2022.1.2 or 2022.2.0-2022.2.1) or Parasolid (any version in the listed vulnerable ranges) is installed with X_T parsing capability.

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 the patched versions: Parasolid V33.1.263+, V34.0.252+, V34.1.242+, V35.0.164+; Simcenter Femap V2022.1.3+, V2022.2.2+. Until patched, avoid opening untrusted X_T files.

Recommended fix High confidence

Simcenter Femap 2022.1.3 or 2022.2.2; Parasolid 33.1.263, 34.0.252, 34.1.242, or 35.0.164 (depending on version branch)

  1. Identify the current Parasolid or Simcenter Femap version in use
  2. For Simcenter Femap: If using version 2022.1.x, upgrade to version 2022.1.3; if using version 2022.2.x, upgrade to version 2022.2.2
  3. For Parasolid: If using version 33.1.x, upgrade to version 33.1.263; if using version 34.0.x, upgrade to version 34.0.252; if using version 34.1.x, upgrade to version 34.1.242; if using version 35.0.x, upgrade to version 35.0.164
  4. Obtain the update from Siemens official channels or your existing support agreement
  5. Test the upgrade in a non-production environment before deploying to production
Caveat Review release notes for compatibility considerations with existing workflows and dependent software

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
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,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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