# CVE-2024-24051: Other in n/a

> Attackers can cause physical damage or malfunction by sending malicious G-code files that move printer parts beyond safe limits.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jun 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-cjpf-prr4-vrfm

## What is CVE-2024-24051?

CVE-2024-24051 is a medium-severity vulnerability in n/a, published on 12 Jun 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

Improper input validation of printing files in Monoprice Select Mini V2 V37.115.32 allows attackers to instruct the device's movable parts to destinations that exceed the devices' maximum coordinates via the printing of a malicious .gcode file.

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

It affects 1 product.


Products: Monoprice Select Mini 3d Printer V2 Firmware.

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

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

## Is CVE-2024-24051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24051 is a medium-severity vulnerability in n/a, published on 12 Jun 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-24051 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-24051/ (Markdown: https://insights.sbomify.com/CVE-2024-24051/index.md)
```

## Sources

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

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