# CVE-2018-10612: Misconfiguration in 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0

> Attackers can access devices and sensitive data because user access management and encryption are disabled by default in CODESYS Control.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 29 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hvp9-xhr6-2xm4

## What is CVE-2018-10612?

CVE-2018-10612 is a critical vulnerability in Codesys Control for Beaglebone Sl, published on 29 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encryption is not enabled by default, which could allow an attacker access to the device and sensitive information, including user credentials.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-311 (Missing Encryption of Sensitive Data), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2018-10612?

It affects 12 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 Rte Sl, Codesys Control Runtime Toolkit, Codesys Control Win Sl, Codesys Development System V3, Codesys Hmi Sl.

## How do I fix CVE-2018-10612?

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

## Is CVE-2018-10612 being exploited?

There is no known exploitation of CVE-2018-10612 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-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)
- [CVE-2022-47380](https://insights.sbomify.com/CVE-2022-47380/): CODESYS: Multiple products prone to out-of-bounds write (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10612 and fix it if it is affected.

What it is: CVE-2018-10612 is a critical vulnerability in Codesys Control for Beaglebone Sl, published on 29 Jan 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-2018-10612 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-2018-10612/ (Markdown: https://insights.sbomify.com/CVE-2018-10612/index.md)
```

## Sources

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

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