# CVE-2024-41176: Beckhoff: Local Denial of Service issue in package MDP included in TwinCAT/BSD

> A local attacker can cause a denial of service and execute code as root via a crafted HTTP request in the MDP package.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2024
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-2fx8-5w8c-86ff

## What is CVE-2024-41176?

CVE-2024-41176 is a high-severity denial of service vulnerability in Beckhoff MDP package, published on 27 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The MPD package included in TwinCAT/BSD allows an authenticated, low-privileged local
attacker to induce a Denial-of-Service (DoS) condition on the daemon and execute code in
the context of user “root” via a crafted HTTP request.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 2 products.


Products: Beckhoff Mdp Package, Beckhoff Twincat\/Bsd.

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

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

## Is CVE-2024-41176 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41176 is a high-severity denial of service vulnerability in Beckhoff MDP package, published on 27 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41176 in the wild and no public exploit code.

Affected product: Beckhoff MDP package. 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-41176/ (Markdown: https://insights.sbomify.com/CVE-2024-41176/index.md)
```

## Sources

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

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