# CVE-2022-47383: CODESYS: Multiple products prone to stack based out-of-bounds write

> Authenticated remote attackers can exploit a stack-based out-of-bounds write in CODESYS products to cause denial of service or execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2023
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-95v4-6244-m56f

## What is CVE-2022-47383?

CVE-2022-47383 is a high-severity memory corruption vulnerability in Codesys Control for Beaglebone Sl, published on 15 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated, remote attacker may use a stack based out-of-bounds write vulnerability in the CmpTraceMgr Component of multiple CODESYS products in multiple versions to write data into the stack which can lead to a denial-of-service condition, memory overwriting, or remote code execution.

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

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

It affects 17 products.


Products: Codesys Control for Beaglebone Sl, Codesys Control for Empc-A\/Imx6 Sl, Codesys Control for Iot2000 Sl, Codesys Control for Linux Sl, Codesys Control for Pfc100 Sl, Codesys Control for Pfc200 Sl, Codesys Control for Plcnext Sl, Codesys Control for Raspberry Pi Sl, Codesys Control for Wago Touch Panels 600 Sl, Codesys Control Rte \(For Beckhoff Cx\) Sl, Codesys Control Rte \(Sl\), Codesys Control Runtime System Toolkit, Codesys Control Win \(Sl\), Codesys Development System V3, Codesys Hmi \(Sl\), Codesys Safety Sil2 Psp, Codesys Safety Sil2 Runtime Toolkit.

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

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

## Is CVE-2022-47383 being exploited?

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

## Other vulnerabilities in Codesys Control for Beaglebone Sl

- [CVE-2019-9010](https://insights.sbomify.com/CVE-2019-9010/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-10612](https://insights.sbomify.com/CVE-2018-10612/): Misconfiguration in 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0 (critical 9.8)
- [CVE-2023-6357](https://insights.sbomify.com/CVE-2023-6357/): OS Command Injection in multiple CODESYS products (high 8.8)
- [CVE-2022-4046](https://insights.sbomify.com/CVE-2022-4046/): CODESYS: Improper memory restrictions fro CODESYS Control (high 8.8)
- [CVE-2022-47379](https://insights.sbomify.com/CVE-2022-47379/): CODESYS: Multiple products prone to out-of-bounds write (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47383 is a high-severity memory corruption vulnerability in Codesys Control for Beaglebone Sl, published on 15 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47383 in the wild and no public exploit code.

Affected product: Codesys Control for Beaglebone Sl. 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-47383/ (Markdown: https://insights.sbomify.com/CVE-2022-47383/index.md)
```

## Sources

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

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