# CVE-2024-43402: Rust OS Command Injection/Argument Injection vulnerability > Attackers can execute arbitrary commands on Windows by exploiting incomplete argument escaping in Rust's process invocation when batch file names contain trailing whitespace or periods. - **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 4 Sep 2024 - **Updated:** 4 Sep 2024 - **Also known as:** GHSA-2xg3-7mm6-98jj ## What is CVE-2024-43402? CVE-2024-43402 is a high-severity command injection vulnerability in rust-lang rust, published on 4 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Rust is a programming language. The fix for CVE-2024-24576, where `std::process::Command` incorrectly escaped arguments when invoking batch files on Windows, was incomplete. Prior to Rust version 1.81.0, it was possible to bypass the fix when the batch file name had trailing whitespace or periods (which are ignored and stripped by Windows). To determine whether to apply the `cmd.exe` escaping rules, the original fix for the vulnerability checked whether the command name ended with `.bat` or `.cmd`. At the time that seemed enough, as we refuse to invoke batch scripts with no file extension. Windows removes trailing whitespace and periods when parsing file paths. For example, `.bat. .` is interpreted by Windows as `.bat`, but the original fix didn't check for that. Affected users who are using Rust 1.77.2 or greater can remove the trailing whitespace (ASCII 0x20) and trailing periods (ASCII 0x2E) from the batch file name to bypass the incomplete fix and enable the mitigations. Users are affected if their code or one of their dependencies invoke a batch script on Windows with trailing whitespace or trailing periods in the name, and pass untrusted arguments to it. Rust 1.81.0 will update the standard library to apply the CVE-2024-24576 mitigations to all batch files invocations, regardless of the trailing chars in the file name. 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-43402? It affects 1 product. Products: Rust-Lang Rust. ## How do I fix CVE-2024-43402? No fix has been published for CVE-2024-43402 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-43402 being exploited? There is no known exploitation of CVE-2024-43402 in the wild and no public exploit code. ## Other vulnerabilities in rust-lang rust - [CVE-2020-36318](https://insights.sbomify.com/CVE-2020-36318/): Use after free in n/a (critical 9.8) - [CVE-2018-1000810](https://insights.sbomify.com/CVE-2018-1000810/): Integer overflow in n/a (critical 9.8) - [CVE-2021-29922](https://insights.sbomify.com/CVE-2021-29922/): Security feature bypass in n/a (critical 9.1) - [CVE-2018-1000657](https://insights.sbomify.com/CVE-2018-1000657/): Memory corruption in n/a (high 7.8) - [CVE-2018-1000622](https://insights.sbomify.com/CVE-2018-1000622/): Other in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-43402 and fix it if it is affected. What it is: CVE-2024-43402 is a high-severity command injection vulnerability in rust-lang rust, published on 4 Sep 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-43402 in the wild and no public exploit code. Affected product: rust-lang rust. 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-43402/ (Markdown: https://insights.sbomify.com/CVE-2024-43402/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43402 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43402 - OSV: https://osv.dev/vulnerability/CVE-2024-43402 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-43402/ Summaries are generated and may contain mistakes; the official description above is the record.