CVE-2024-27308
Mio's tokens for named pipes may be delivered after deregistration
Reported by github_m · Published March 6, 2024
mio is fixed in 0.8.11 (crates.io)
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| mio | crates.io | 0.8.11 |
| pgcat | Wolfi | 1.2.0-r1 |
| linkerd-network-validator | Wolfi | 0.1.2-r2 |
| pgcat | Chainguard | 1.2.0-r1 |
| linkerd-network-validator | Chainguard | 0.1.2-r2 |
| topgrade | Wolfi | 15.0.0-r0 |
| mio | mio_project | 0.8.10 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| tokio-rs | mio | >= 0.7.2, < 0.8.11 |
| wolfi | pgcat | 0 |
| wolfi | linkerd-network-validator | 0 |
| chainguard | pgcat | 0 |
| chainguard | linkerd-network-validator | 0 |
| wolfi | topgrade | 0 |
| tokio-rs | mio | 0.7.2 |
| crates.io | mio | 0.7.2 |
| mio_project | mio | 0.7.2 |
| wolfi | pulumi-watch | 0 |
| chainguard | topgrade | 0 |
| wolfi | cargo-audit | 0 |
| chainguard | berg | 0 |
| chainguard | cargo-audit | 0 |
| wolfi | kdash | 0 |
| wolfi | zellij | 0 |
| chainguard | zellij | 0 |
| chainguard | pulumi-watch | 0 |
| chainguard | kdash | 0 |
| wolfi | berg | 0 |
Timeline
- Mar 1, 2024 Fix PR Merged
- Mar 4, 2024 CVE Published
- Mar 7, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (9 in total, the first dated here)
- Jan 15, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-27308
vulnetix vdb fixes CVE-2024-27308
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-27308/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7 x_refsource_CONFIRM
- https://github.com/tokio-rs/tokio/issues/6369 x_refsource_MISC
- https://github.com/tokio-rs/mio/pull/1760 x_refsource_MISC
- https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9 x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2024-27308 advisory
- https://github.com/advisories/GHSA-r8w9-5wcg-vfj7 advisory
- https://github.com/tokio-rs/mio url