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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2024-03-06T19:27:28.521Z

Updated: 2024-08-27T16:47:28.665Z

Reserved: 2024-02-22T18:08:38.876Z

Link: CVE-2024-27308

cve-icon Vulnrichment

Updated: 2024-08-02T00:28:00.264Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-03-06T20:15:47.730

Modified: 2024-03-06T21:42:48.053

Link: CVE-2024-27308

cve-icon Redhat

No data.