# CVE-2024-8934: Beckhoff: Local command injection via TwinCAT Package Manager

> A local administrator can execute arbitrary OS commands via crafted UI settings in the TwinCAT Package Manager.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-w672-pp4p-44p3

## What is CVE-2024-8934?

CVE-2024-8934 is a medium-severity command injection vulnerability in Beckhoff TwinCAT Package Manager, published on 31 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A local user with administrative access rights can enter specialy crafted values for settings at the user interface (UI) of the TwinCAT Package Manager which then causes arbitrary OS commands to be executed.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-8934 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8934 is a medium-severity command injection vulnerability in Beckhoff TwinCAT Package Manager, published on 31 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-8934 in the wild and no public exploit code.

Affected product: Beckhoff TwinCAT Package Manager. 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-8934/ (Markdown: https://insights.sbomify.com/CVE-2024-8934/index.md)
```

## Sources

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

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