# CVE-2024-5000: CODESYS: Incorrect calculation of buffer size can cause DoS on CODESYS OPC UA products

> An unauthenticated remote attacker can cause a denial of service on CODESYS OPC UA products by sending a crafted request that triggers a buffer size calculation error.

- **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:** 4 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-xchm-28cx-p56h

## What is CVE-2024-5000?

CVE-2024-5000 is a high-severity denial of service vulnerability in CODESYS Control RTE (SL), published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can use a malicious OPC UA client to send a crafted request to affected CODESYS products which can cause a DoS due to incorrect calculation of buffer size.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

## Which versions are affected by CVE-2024-5000?


## How do I fix CVE-2024-5000?

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

## Is CVE-2024-5000 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5000 and fix it if it is affected.

What it is: CVE-2024-5000 is a high-severity denial of service vulnerability in CODESYS Control RTE (SL), published on 4 Jun 2024. 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-2024-5000 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-2024-5000/ (Markdown: https://insights.sbomify.com/CVE-2024-5000/index.md)
```

## Sources

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

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