dbcve.org
Simcenter FemapApplication · Siemens

CVE-2022-39137

HIGH · 7.8 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to 33.1.262 / 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 V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.161), 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. An attacker could leverage this vulnerability to leak information in the context of the current process. (ZDI-CAN-17276)

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 is an out-of-bounds read past the end of an allocated buffer when parsing X_T files in Parasolid and Simcenter Femap. An attacker can exploit this to leak sensitive information from the process memory by tricking a user into opening a malicious X_T file.

MitigationUpdate to the patched versions: Parasolid V33.1.262+, V34.0.252+, V34.1.242+, V35.0.161+ or Simcenter Femap V2022.1.3+, V2022.2.2+. 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.262>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.161

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 Femap, or right-click the femap.exe file and select Properties > Details to view the product version
    Affected if Version is 2022.1.x where x < 3, or 2022.2.x where x < 2
  2. Check Parasolid library version
    Locate the Parasolid DLL (typically psparasolid.dll or similar) used by your application. Right-click the DLL, select Properties > Details to view the File Version
    Affected if Version is 33.1.x where x < 262, 34.0.x where x < 252, 34.1.x where x < 242, or 35.0.x where x < 161
  3. Verify X_T file handling is available
    Confirm that your Femap or Parasolid-based application can open .x_t files. Try opening a benign X_T file or check file association settings
    Affected if The application supports X_T file parsing, which is a standard feature enabling the vulnerable code path
  4. Identify if Simcenter Femap or Parasolid-based application is in use
    Check installed programs list for Siemens Simcenter Femap, or identify if your CAD/CAE application uses Parasolid as its kernel (check documentation or vendor)
    Affected if Any application using vulnerable Parasolid versions or running vulnerable Femap versions is present

You are affected if Simcenter Femap version is below 2022.1.3 or 2022.2.2, OR Parasolid library version is below 33.1.262, 34.0.252, 34.1.242, or 35.0.161, and the application can 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.262 / 34.0.252 / 34.1.242 or later
Fixed in 33.1.26234.0.25234.1.242
Interim mitigation

Update to the patched versions: Parasolid V33.1.262+, V34.0.252+, V34.1.242+, V35.0.161+ or Simcenter Femap V2022.1.3+, V2022.2.2+. Avoid opening untrusted X_T files.

Recommended fix High confidence

Simcenter Femap V2022.1.3 or V2022.2.2; Parasolid V33.1.262 / V34.0.252 / V34.1.242 / V35.0.161

  1. 1. Identify the currently installed version of Simcenter Femap or Parasolid by checking the application's About/Help section
  2. 2. If using Simcenter Femap V2022.1.x (versions before V2022.1.3), upgrade to V2022.1.3 or later
  3. 3. If using Simcenter Femap V2022.2.x (versions before V2022.2.2), upgrade to V2022.2.2 or later
  4. 4. For Parasolid integrations, upgrade to the appropriate fixed version: V33.1.262, V34.0.252, V34.1.242, or V35.0.161 depending on the major version line in use
  5. 5. Obtain the update from the Siemens PLM Customer Portal or through your standard software distribution channel
  6. 6. After upgrading, validate that X_T file parsing functions correctly and the vulnerability is remediated

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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