First published: Wed Sep 04 2024(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Rust | <1.81.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-43402 is considered to have a moderate severity due to the potential for bypassing security measures.
To fix CVE-2024-43402, upgrade Rust to version 1.81.0 or later where the vulnerability has been addressed.
CVE-2024-43402 affects users of Rust versions prior to 1.81.0.
CVE-2024-43402 is caused by an incomplete fix for argument escaping in `std::process::Command` when invoking batch files on Windows.
Yes, CVE-2024-43402 is related to CVE-2024-24576 as it stems from an incomplete fix for that earlier vulnerability.