VDB

CVE-2024-27308

CVE-2024-27308 PUBLISHED CVSS 7.5 HIGH

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.

PackageEcosystemFixed in
miocrates.io0.8.11
pgcatWolfi1.2.0-r1
linkerd-network-validatorWolfi0.1.2-r2
pgcatChainguard1.2.0-r1
linkerd-network-validatorChainguard0.1.2-r2
topgradeWolfi15.0.0-r0
miomio_project0.8.10

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

VendorProductVersions
tokio-rsmio>= 0.7.2, < 0.8.11
wolfipgcat0
wolfilinkerd-network-validator0
chainguardpgcat0
chainguardlinkerd-network-validator0
wolfitopgrade0
tokio-rsmio0.7.2
crates.iomio0.7.2
mio_projectmio0.7.2
wolfipulumi-watch0
chainguardtopgrade0
wolficargo-audit0
chainguardberg0
chainguardcargo-audit0
wolfikdash0
wolfizellij0
chainguardzellij0
chainguardpulumi-watch0
chainguardkdash0
wolfiberg0

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

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›