# CVE-2022-45147: Deserialization in SIMATIC PCS neo V4.0

> An attacker can execute arbitrary code by exploiting unsafe .NET BinaryFormatter deserialization in Siemens SIMATIC applications.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 9 Jul 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-mrhc-f9rh-fm9r

## What is CVE-2022-45147?

CVE-2022-45147 is a high-severity unsafe deserialization vulnerability in Siemens SIMATIC PCS neo V4.0, published on 9 Jul 2024. 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 SIMATIC PCS neo V4.0 (All versions), SIMATIC STEP 7 V16 (All versions), SIMATIC STEP 7 V17 (All versions), SIMATIC STEP 7 V18 (All versions < V18 Update 2). Affected applications do not properly restrict the .NET BinaryFormatter when deserializing user-controllable input. This could allow an attacker to cause a type confusion and execute arbitrary code within the affected application.

This is the same issue that exists for .NET BinaryFormatter https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2300.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2022-45147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45147 is a high-severity unsafe deserialization vulnerability in Siemens SIMATIC PCS neo V4.0, published on 9 Jul 2024. 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-45147 in the wild and no public exploit code.

Affected product: Siemens SIMATIC PCS neo V4.0. 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-45147/ (Markdown: https://insights.sbomify.com/CVE-2022-45147/index.md)
```

## Sources

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

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