# CVE-2019-9012: Denial of service in n/a

> A crafted communication request causes uncontrolled memory allocations in CODESYS V3 products, leading to a denial-of-service condition.

- **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:** 15 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q2jg-8rwm-9rgx

## What is CVE-2019-9012?

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

### Official description

An issue was discovered in 3S-Smart CODESYS V3 products. A crafted communication request may cause uncontrolled memory allocations in the affected CODESYS products and may result in a denial-of-service condition. All variants of the following CODESYS V3 products in all versions prior to v3.5.14.20 that contain the CmpGateway 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 PFC100, CODESYS Control for PFC200, CODESYS Control for Raspberry Pi, CODESYS Control V3 Runtime System Toolkit, CODESYS Gateway V3, CODESYS V3 Development System.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 10 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 Raspberry Pi Sl, Codesys Control Runtime Toolkit, Codesys Development System, Codesys Gateway.

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

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

## Is CVE-2019-9012 being exploited?

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

What it is: CVE-2019-9012 is a high-severity denial of service vulnerability in Codesys Control for Beaglebone Sl, published on 15 Aug 2019. 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-9012 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-2019-9012/ (Markdown: https://insights.sbomify.com/CVE-2019-9012/index.md)
```

## Sources

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

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