End of life: 5/15/2025, Latest version: 1.86.0
End of life: 4/3/2025, Latest version: 1.85.1
End of life: 2/20/2025, Latest version: 1.84.1
End of life: 2/20/2025, Latest version: 1.84.1
End of life: 1/9/2025, Latest version: 1.83.0
End of life: 1/9/2025, Latest version: 1.83.0
End of life: 11/28/2024, Latest version: 1.82.0
End of life: 11/28/2024, Latest version: 1.82.0
End of life: 10/17/2024, Latest version: 1.81.0
End of life: 10/17/2024, Latest version: 1.81.0
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.
End of life: 9/5/2024, Latest version: 1.80.1
End of life: 9/5/2024, Latest version: 1.80.1
End of life: 7/25/2024, Latest version: 1.79.0
End of life: 7/25/2024, Latest version: 1.79.0
End of life: 6/13/2024, Latest version: 1.78.0
End of life: 6/13/2024, Latest version: 1.78.0
End of life: 5/2/2024, Latest version: 1.77.2
End of life: 5/2/2024, Latest version: 1.77.2
End of life: 3/21/2024, Latest version: 1.76.0
End of life: 3/21/2024, Latest version: 1.76.0
End of life: 2/8/2024, Latest version: 1.75.0
End of life: 2/8/2024, Latest version: 1.75.0
Impact Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
Patches No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
Workarounds The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
References This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.
- https://rustsec.org/advisories/RUSTSEC-2023-0071.html - https://people.redhat.com/~hkario/marvin/ - https://github.com/RustCrypto/RSA/issues/19
End of life: 12/28/2023, Latest version: 1.74.1
End of life: 12/28/2023, Latest version: 1.74.1
End of life: 11/17/2023, Latest version: 1.73.0
End of life: 11/17/2023, Latest version: 1.73.0
The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).