# CVE-2022-2561: Deserialization in QuickOPC

> Remote attackers can execute arbitrary code via malicious XML files in OPC Labs QuickOPC, requiring user interaction to open the file.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 29 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-mw6v-8jv9-7qrx

## What is CVE-2022-2561?

CVE-2022-2561 is a high-severity unsafe deserialization vulnerability in QuickOPC, published on 29 Mar 2023. 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

This vulnerability allows remote attackers to execute arbitrary code on affected installations of OPC Labs QuickOPC 2022.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of XML files in Connectivity Explorer. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16596.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Opclabs Quickopc.

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

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

## Is CVE-2022-2561 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2561 is a high-severity unsafe deserialization vulnerability in QuickOPC, published on 29 Mar 2023. 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-2561 in the wild and no public exploit code.

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

## Sources

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

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