# CVE-2022-22517: Communication Components in multiple CODESYS products vulnerable to communication channel disruption

> Remote attackers can disrupt communication channels in CODESYS products by guessing IDs and injecting packets, causing service denial.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 7 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-95jh-v98h-7gww

## What is CVE-2022-22517?

CVE-2022-22517 is a high-severity denial of service vulnerability in Codesys Control for Beaglebone Sl, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated, remote attacker can disrupt existing communication channels between CODESYS products by guessing a valid channel ID and injecting packets. This results in the communication channel to be closed.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-334 (Small Space of Random Values)

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

It affects 20 products.


Products: Codesys Control for Beaglebone Sl, Codesys Control for Beckhoff Cx9020, 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 Sl, Codesys Control Rte Sl \(For Beckhoff Cx\), Codesys Control Runtime System Toolkit, Codesys Control Win Sl, Codesys Development System, Codesys Edge Gateway, Codesys Embedded Target Visu Toolkit, Codesys Gateway, Codesys Hmi Sl, Codesys Remote Target Visu Toolkit.

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

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

## Is CVE-2022-22517 being exploited?

There is no known exploitation of CVE-2022-22517 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-22517 and fix it if it is affected.

What it is: CVE-2022-22517 is a high-severity denial of service vulnerability in Codesys Control for Beaglebone Sl, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22517 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-22517/ (Markdown: https://insights.sbomify.com/CVE-2022-22517/index.md)
```

## Sources

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

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