# CVE-2019-5105: Memory corruption in 3S

> A specially crafted packet causes memory corruption in CODESYS GatewayService, leading to process termination and denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 26 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fhfx-4gh6-9wc2

## What is CVE-2019-5105?

CVE-2019-5105 is a high-severity memory corruption vulnerability in 3S, published on 26 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable memory corruption vulnerability exists in the Name Service Client functionality of 3S-Smart Software Solutions CODESYS GatewayService. A specially crafted packet can cause a large memcpy, resulting in an access violation and termination of the process. An attacker can send a packet to a device running the GatewayService.exe to trigger this vulnerability. All variants of the CODESYS V3 products in all versions prior V3.5.16.10 containing the CmpRouter or CmpRouterEmbedded component are affected, regardless of the CPU type or operating system: CODESYS Control for BeagleBone, CODESYS Control for emPC-A/iMX6, CODESYS Control for IOT2000, CODESYS Control for Linux, CODESYS Control for PLCnext, CODESYS Control for PFC100, CODESYS Control for PFC200, CODESYS Control for Raspberry Pi, CODESYS Control RTE V3, CODESYS Control RTE V3 (for Beckhoff CX), CODESYS Control Win V3 (also part of the CODESYS Development System setup), CODESYS Control V3 Runtime System Toolkit, CODESYS V3 Embedded Target Visu Toolkit, CODESYS V3 Remote Target Visu Toolkit, CODESYS V3 Safety SIL2, CODESYS Edge Gateway V3, CODESYS Gateway V3, CODESYS HMI V3, CODESYS OPC Server V3, CODESYS PLCHandler SDK, CODESYS V3 Simulation Runtime (part of the CODESYS Development System).

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-5105?

It affects 1 product.


Products: Codesys Codesys.

## How do I fix CVE-2019-5105?

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

## Is CVE-2019-5105 being exploited?

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

## Other vulnerabilities in 3S

- [CVE-2019-16265](https://insights.sbomify.com/CVE-2019-16265/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-34584](https://insights.sbomify.com/CVE-2021-34584/): CODESYS V2 web server: crafted requests could trigger a buffer over-read (DoS) (critical 9.1)
- [CVE-2021-21869](https://insights.sbomify.com/CVE-2021-21869/): Deserialization in CODESYS (high 8.8)
- [CVE-2021-21867](https://insights.sbomify.com/CVE-2021-21867/): Deserialization in CODESYS (high 8.8)
- [CVE-2021-21868](https://insights.sbomify.com/CVE-2021-21868/): Deserialization in CODESYS (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5105 and fix it if it is affected.

What it is: CVE-2019-5105 is a high-severity memory corruption vulnerability in 3S, published on 26 Mar 2020. 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-2019-5105 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-2019-5105/ (Markdown: https://insights.sbomify.com/CVE-2019-5105/index.md)
```

## Sources

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

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