CVE-2024-24576
A public proof of concept exists; no exploitation attested.
- Published2024-04-09
- WeaknessCWE-78 · CWE-88
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2024-04-0918:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-24576?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-24576?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 38.x | = 38 | no fix published | NVD |
| 39.x | = 39 | no fix published | NVD |
| 40.x | = 40 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.77 | < 1.77.2 | 1.77.2 | NVD · CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- github.comMitigation · Vendor Advisory
- lists.fedoraproject.orgVendor Advisory
- lists.fedoraproject.orgVendor Advisory
- lists.fedoraproject.orgVendor Advisory
Detection
read 2026-10-23 19:24 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 7 repositories, unverifiedfrostb1ten/CVE-2024-24576-PoCbrains93/CVE-2024-24576-PoC-Pythonaydinnyunus/CVE-2024-24576-Exploitfoxoman/CVE-2024-24576-PoC---Nimlpn/CVE-2024-24576.jl PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionpoc2025-02-26
- OpenCVESSVC decisionpoc—
- CNACVSS 3.110read 2026-10-23
- NVDCVSS 3.110read 2026-10-23
- CNAweakness (CWE)CWE-78, CWE-88read 2026-10-23
- NVDweakness (CWE)CWE-78read 2026-10-23
- FIRST EPSSEPSS score20.3 %read 2026-10-23
- PoC-in-GitHubproof of concept7read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Published
- 2024-04-09
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2024-24576?
Is CVE-2024-24576 actively exploited?
What is the CVSS score for CVE-2024-24576?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.