# CVE-2024-51330: Code injection in n/a

> A local attacker can execute arbitrary code via IPC mechanisms in UltiMaker Cura, affecting users of the 3D printing software.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-29fm-rc5r-j557

## What is CVE-2024-51330?

CVE-2024-51330 is a medium-severity code injection vulnerability in n/a, published on 15 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in UltiMaker Cura v.4.41 and 5.8.1 and before allows a local attacker to execute arbitrary code via Inter-process communication (IPC) mechanism between Cura application and CuraEngine processes, localhost network stack, printing settings and G-code processing and transmission components, Ultimaker 3D Printers.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ultimaker Ultimaker Cura.

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

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

## Is CVE-2024-51330 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-8374](https://insights.sbomify.com/CVE-2024-8374/): Arbitrary Code Injection in Cura (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51330 is a medium-severity code injection vulnerability in n/a, published on 15 Nov 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-51330 in the wild and no public exploit code.

Affected product: n/a. 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-51330/ (Markdown: https://insights.sbomify.com/CVE-2024-51330/index.md)
```

## Sources

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

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