# CVE-2022-39151: Memory corruption in Parasolid V33.1

> An out-of-bounds write in Siemens Parasolid and Femap allows attackers to execute arbitrary code via crafted X_T files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2022
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-fcrq-3q8j-4j94

## What is CVE-2022-39151?

CVE-2022-39151 is a high-severity memory corruption vulnerability in Siemens Parasolid, published on 13 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-39151?

It affects 2 products.


Products: Siemens Parasolid, Siemens Simcenter Femap.

## How do I fix CVE-2022-39151?

No fix has been published for CVE-2022-39151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-39151 being exploited?

There is no known exploitation of CVE-2022-39151 in the wild and no public exploit code.

## Other vulnerabilities in Siemens Parasolid

- [CVE-2024-31980](https://insights.sbomify.com/CVE-2024-31980/): Memory corruption in Parasolid V35.1 (high 7.8)
- [CVE-2023-49125](https://insights.sbomify.com/CVE-2023-49125/): Memory corruption in Parasolid V35.0 (high 7.8)
- [CVE-2023-45601](https://insights.sbomify.com/CVE-2023-45601/): Memory corruption in Parasolid V35.0 (high 7.8)
- [CVE-2023-41032](https://insights.sbomify.com/CVE-2023-41032/): Memory corruption in Parasolid V34.1 (high 7.8)
- [CVE-2023-41033](https://insights.sbomify.com/CVE-2023-41033/): Memory corruption in Parasolid V35.0 (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39151 and fix it if it is affected.

What it is: CVE-2022-39151 is a high-severity memory corruption vulnerability in Siemens Parasolid, published on 13 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-39151 in the wild and no public exploit code.

Affected product: Siemens Parasolid. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39151/ (Markdown: https://insights.sbomify.com/CVE-2022-39151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39151
- OSV: https://osv.dev/vulnerability/CVE-2022-39151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39151/
Summaries are generated and may contain mistakes; the official description above is the record.