CVE-2024-27308 Mio's tokens for named pipes may be delivered after deregistration
Attackers can trigger use-after-free in Tokio applications on Windows by exploiting invalid named pipe tokens in the Mio library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-27308?
CVE-2024-27308 is a high-severity use after free vulnerability in tokio-rs mio, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Mio is a Metal I/O library for Rust. When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free. For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio. The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected. This vulnerability has been fixed in mio v0.8.11. All versions of mio between v0.7.2 and v0.8.10 are vulnerable. Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable. Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.
Which versions are affected by CVE-2024-27308?
3 open source packages ship an affected version, including mio. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
mio crates.io | From 0.7.2 | 0.8.11 |
mio crates.io | From 0.7.2 | 0.8.11 |
mio crates.io | From 0.7.2 | 0.8.11 |
Products include Mio Project Mio, Tokio Tokio.
How do I fix CVE-2024-27308?
Upgrade mio to 0.8.11 or later.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2024-27308 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27308 exists.
Other vulnerabilities in tokio-rs mio
Sources
Also known as AZL-35748, AZL-61991, GHSA-r8w9-5wcg-vfj7, RUSTSEC-2024-0019.