# CVE-2024-24576: Rusts's `std::process::Command` did not properly escape arguments of batch files on Windows > Attackers can execute arbitrary shell commands on Windows by bypassing argument escaping in Rust's Command API when invoking batch files. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Apr 2024 - **Updated:** 4 Nov 2025 - **Also known as:** GHSA-q455-m56c-85mh, MGASA-2025-0136, openSUSE-SU-2024:13966-1 ## What is CVE-2024-24576? CVE-2024-24576 is a critical command injection vulnerability in Fedoraproject Fedora, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Rust is a programming language. The Rust Security Response WG was notified that the Rust standard library prior to version 1.77.2 did not properly escape arguments when invoking batch files (with the `bat` and `cmd` extensions) on Windows using the `Command`. An attacker able to control the arguments passed to the spawned process could execute arbitrary shell commands by bypassing the escaping. The severity of this vulnerability is critical for those who invoke batch files on Windows with untrusted arguments. No other platform or use is affected. The `Command::arg` and `Command::args` APIs state in their documentation that the arguments will be passed to the spawned process as-is, regardless of the content of the arguments, and will not be evaluated by a shell. This means it should be safe to pass untrusted input as an argument. On Windows, the implementation of this is more complex than other platforms, because the Windows API only provides a single string containing all the arguments to the spawned process, and it's up to the spawned process to split them. Most programs use the standard C run-time argv, which in practice results in a mostly consistent way arguments are splitted. One exception though is `cmd.exe` (used among other things to execute batch files), which has its own argument splitting logic. That forces the standard library to implement custom escaping for arguments passed to batch files. Unfortunately it was reported that our escaping logic was not thorough enough, and it was possible to pass malicious arguments that would result in arbitrary shell execution. Due to the complexity of `cmd.exe`, we didn't identify a solution that would correctly escape arguments in all cases. To maintain our API guarantees, we improved the robustness of the escaping code, and changed the `Command` API to return an `InvalidInput` error when it cannot safely escape an argument. This error will be emitted when spawning the process. The fix is included in Rust 1.77.2. Note that the new escaping logic for batch files errs on the conservative side, and could reject valid arguments. Those who implement the escaping themselves or only handle trusted inputs on Windows can also use the `CommandExt::raw_arg` method to bypass the standard library's escaping logic. Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2024-24576? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rust1.77` | openSUSE:Tumbleweed | All versions | 1.77.2-1.1 | Products: Fedoraproject Fedora, Rust-Lang Rust. ## How do I fix CVE-2024-24576? Upgrade to a fixed version. ## Is CVE-2024-24576 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24576 exists. Public exploit code: - Example of CVE-2024-24576 use case. (github_poc): https://github.com/frostb1ten/CVE-2024-24576-PoC - CVE-2024-24576 Proof of Concept (github_poc): https://github.com/aydinnyunus/CVE-2024-24576-Exploit - https://github.com/brains93/CVE-2024-24576-PoC-Python (github_poc): https://github.com/brains93/CVE-2024-24576-PoC-Python - Simple CVE-2024-24576 PoC in Julia (github_poc): https://github.com/lpn/CVE-2024-24576.jl - CVE-2024-24576 PoC for Nim Lang (github_poc): https://github.com/foxoman/CVE-2024-24576-PoC---Nim - https://github.com/Gaurav1020/CVE-2024-24576-PoC-Rust (github_poc): https://github.com/Gaurav1020/CVE-2024-24576-PoC-Rust ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-24576 and fix it if it is affected. What it is: CVE-2024-24576 is a critical command injection vulnerability in Fedoraproject Fedora, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24576 exists. Affected product: Fedoraproject Fedora. 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-24576/ (Markdown: https://insights.sbomify.com/CVE-2024-24576/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24576 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24576 - OSV: https://osv.dev/vulnerability/CVE-2024-24576 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-24576/ Summaries are generated and may contain mistakes; the official description above is the record.