CVE-2022-39141
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 · uneditedA 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-17296)
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 confidenceParasolid and Simcenter Femap contain an out-of-bounds read vulnerability when parsing X_T files, allowing an attacker to read memory beyond allocated buffers and leak sensitive information in the context of the current process.
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>= 2022.1, < 2022.1.3>= 2022.2, < 2022.2.2>= 33.1, < 33.1.262>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.161CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Simcenter Femap versionLocate the Simcenter Femap installation and determine its version number. On Windows, open Add/Remove Programs and find Simcenter Femap, or launch the application and go to Help > About to view the exact version (such as 2022.1 or 2022.2). Record the full version string including any sub-version numbers.Affected if Version is 2022.1 through 2022.1.2, or 2022.2 through 2022.2.1 (these fall within the unpatched ranges)
-
Check Parasolid versionIdentify applications that use the Parasolid kernel and determine the Parasolid version they bundle. This information typically appears in the host application's About or Help dialog, often labeled as 'Parasolid version' or 'Kernel version'. Check the application's documentation or bin directory for parasolid DLL version info.Affected if Version is 33.1.x where x is less than 262; 34.0.x where x is less than 252; 34.1.x where x is less than 242; or 35.0.x where x is less than 161
-
Confirm X_T file parsing is availableDetermine if the installed software has the capability to import or open X_T (Parasolid Text) files. Open the application's File > Open or File > Import dialog and look for 'X_T' or 'Parasolid X_T' listed as a supported file format. This is the feature that triggers the vulnerable code path.Affected if X_T file import functionality exists in the product AND the product version falls within the affected ranges
If either Simcenter Femap or Parasolid is installed with an unpatched version AND the software can import or process X_T files, the environment is vulnerable to CVE-2022-39141.
Generated from the published advisory. Verify against your own configuration.
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 · scoped33.1.26234.0.25234.1.242
Update affected products to the patched versions: Parasolid V33.1.262+, V34.0.252+, V34.1.242+, V35.0.161+, Simcenter Femap V2022.1.3+, or V2022.2.2+. Restrict untrusted X_T file sources until updates are applied.
Simcenter Femap: 2022.1.3 or 2022.2.2; Parasolid: 33.1.262 / 34.0.252 / 34.1.242 / 35.0.161 (minimum respective to each major version branch)
- For Simcenter Femap users: Upgrade to version 2022.1.3 or later, or upgrade to version 2022.2.2 or later
- For Parasolid users: Upgrade to version 33.1.262 or later, or version 34.0.252 or later, or version 34.1.242 or later, or version 35.0.161 or later
- After upgrading, verify that X_T file parsing operations work correctly in the updated version
- Consider testing with X_T files from untrusted sources in a controlled environment to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
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 locallyCheck whether your project pulls in CVE-2022-39141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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