# CVE-2020-6081: Code injection in 3S

> Remote attackers can execute arbitrary code on CODESYS Runtime PLCs by sending specially crafted network requests, posing a critical risk to industrial control systems.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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:** 7 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7grw-2xfw-qjvm

## What is CVE-2020-6081?

CVE-2020-6081 is a critical code injection vulnerability in 3S, published on 7 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exploitable code execution vulnerability exists in the PLC_Task functionality of 3S-Smart Software Solutions GmbH CODESYS Runtime 3.5.14.30. A specially crafted network request can cause remote code execution. An attacker can send a malicious packet to trigger this vulnerability.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2020-6081?

It affects 1 product.


Products: Codesys Runtime.

## How do I fix CVE-2020-6081?

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

## Is CVE-2020-6081 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6081 and fix it if it is affected.

What it is: CVE-2020-6081 is a critical code injection vulnerability in 3S, published on 7 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6081 in the wild and no public exploit code.

Affected product: 3S. 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-2020-6081/ (Markdown: https://insights.sbomify.com/CVE-2020-6081/index.md)
```

## Sources

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

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