# CVE-2024-21574: Code injection in ComfyUI-Manager

> Attackers can achieve remote code execution by sending a crafted POST request to the custom node installation endpoint due to missing input validation.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2024
- **Updated:** 12 Dec 2024
- **Also known as:** GHSA-7p9r-9x76-5h9r

## What is CVE-2024-21574?

CVE-2024-21574 is a critical code injection vulnerability in ltdrdata ComfyUI-Manager, published on 12 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The issue stems from a missing validation of the pip field in a POST request sent to the /customnode/install endpoint used to install custom nodes which is added to the server by the extension. This allows an attacker to craft a request that triggers a pip install on a user controlled package or URL, resulting in remote code execution (RCE) on the server.

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

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


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

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

## Is CVE-2024-21574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21574 is a critical code injection vulnerability in ltdrdata ComfyUI-Manager, published on 12 Dec 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-21574 in the wild and no public exploit code.

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

## Sources

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

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