# CVE-2022-22516: CODESYS driver SysDrv3S allows SYSTEM users on Microsoft Windows to read and write in restricted memory space.

> Local attackers can read and write restricted memory via the SysDrv3S driver, enabling privilege escalation in CODESYS Control systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wg22-wcgm-8m72

## What is CVE-2022-22516?

CVE-2022-22516 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 7 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SysDrv3S driver in the CODESYS Control runtime system on Microsoft Windows allows any system user to read and write within restricted memory space.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 4 products.


Products: Codesys Control Rte Sl, Codesys Control Rte Sl \(For Beckhoff Cx\), Codesys Control Win Sl, Codesys Development System.

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

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

## Is CVE-2022-22516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22516 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 7 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22516 in the wild and no public exploit code.

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

## Sources

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

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