# CVE-2022-27580: Deserialization in SICK Safety Designer

> An attacker can execute arbitrary code by tricking a user into opening a malicious project file in SICK Safety Designer.

- **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:** 19 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h8vm-cr7c-cgqx

## What is CVE-2022-27580?

CVE-2022-27580 is a high-severity unsafe deserialization vulnerability in SICK Safety Designer, published on 19 Jul 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 deserialization vulnerability in a .NET framework class used and not properly checked by Safety Designer all versions up to and including 1.11.0 allows an attacker to craft malicious project files. Opening/importing such a malicious project file would execute arbitrary code with the privileges of the current user when opened or imported by the Safety Designer. This compromises confidentiality integrity and availability. For the attack to succeed a user must manually open a malicious project file.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Sick Safety Designer.

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

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

## Is CVE-2022-27580 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27580 is a high-severity unsafe deserialization vulnerability in SICK Safety Designer, published on 19 Jul 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-27580 in the wild and no public exploit code.

Affected product: SICK Safety Designer. 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-27580/ (Markdown: https://insights.sbomify.com/CVE-2022-27580/index.md)
```

## Sources

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

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