# CVE-2023-2003: Embedded malicious code vulnerability in Unitronics Vision1210

> Remote attackers can inject and execute malicious code on Unitronics Vision1210 devices via the PCOM protocol, compromising industrial control systems.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-5746-cm3p-frrh

## What is CVE-2023-2003?

CVE-2023-2003 is a critical code injection vulnerability in Unitronics Vision1210, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Embedded malicious code vulnerability in Vision1210, in the build 5 of operating system version 4.3, which could allow a remote attacker to store base64-encoded malicious code in the device's data tables via the PCOM protocol, which can then be retrieved by a client and executed on the device.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2023-2003?

It affects 1 product.


Products: Unitronics Vision1210 Firmware.

## How do I fix CVE-2023-2003?

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

## Is CVE-2023-2003 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2003 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2003 and fix it if it is affected.

What it is: CVE-2023-2003 is a critical code injection vulnerability in Unitronics Vision1210, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2003 exists.

Affected product: Unitronics Vision1210. 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-2023-2003/ (Markdown: https://insights.sbomify.com/CVE-2023-2003/index.md)
```

## Sources

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

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