CVE-2024-27308
Mio's tokens for named pipes may be delivered after deregistration
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.
INFO
Published Date :
March 6, 2024, 8:15 p.m.
Last Modified :
Dec. 4, 2025, 5:51 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 3.1 | CRITICAL | [email protected] |
Solution
- Update the affected packages.
- If using Tokio, ensure it is version 1.30.0 or later.
Public PoC/Exploit Available at Github
CVE-2024-27308 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-27308.
| URL | Resource |
|---|---|
| https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 | Patch |
| https://github.com/tokio-rs/mio/pull/1760 | Issue Tracking |
| https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 | Vendor Advisory |
| https://github.com/tokio-rs/tokio/issues/6369 | Issue Tracking |
| https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 | Patch |
| https://github.com/tokio-rs/mio/pull/1760 | Issue Tracking |
| https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 | Vendor Advisory |
| https://github.com/tokio-rs/tokio/issues/6369 | Issue Tracking |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-27308 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-27308
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-27308 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-27308 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Dec. 04, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H Added CPE Configuration OR *cpe:2.3:a:mio_project:mio:*:*:*:*:*:rust:*:* versions from (including) 0.7.2 up to (including) 0.8.10 *cpe:2.3:a:tokio:tokio:*:*:*:*:*:rust:*:* versions from (including) 1.30.0 Added Reference Type CVE: https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 Types: Patch Added Reference Type CVE: https://github.com/tokio-rs/mio/pull/1760 Types: Issue Tracking Added Reference Type GitHub, Inc.: https://github.com/tokio-rs/mio/pull/1760 Types: Issue Tracking Added Reference Type CVE: https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 Types: Vendor Advisory Added Reference Type GitHub, Inc.: https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 Types: Vendor Advisory Added Reference Type CVE: https://github.com/tokio-rs/tokio/issues/6369 Types: Issue Tracking Added Reference Type GitHub, Inc.: https://github.com/tokio-rs/tokio/issues/6369 Types: Issue Tracking -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 Added Reference https://github.com/tokio-rs/mio/pull/1760 Added Reference https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 Added Reference https://github.com/tokio-rs/tokio/issues/6369 -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Received by [email protected]
Mar. 06, 2024
Action Type Old Value New Value Added 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. Added Reference GitHub, Inc. https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 [No types assigned] Added Reference GitHub, Inc. https://github.com/tokio-rs/tokio/issues/6369 [No types assigned] Added Reference GitHub, Inc. https://github.com/tokio-rs/mio/pull/1760 [No types assigned] Added Reference GitHub, Inc. https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 [No types assigned] Added CWE GitHub, Inc. CWE-416 Added CWE GitHub, Inc. CWE-672 Added CVSS V3.1 GitHub, Inc. AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N