Skip to main content
Public proof of conceptFix available

CVE-2024-27308

A public proof of concept exists; no exploitation attested.

  • Published2024-03-06
  • Fixed in0.8.11
  • WeaknessCWE-416 · CWE-672

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-03-0620:15CVE publishedNVD

Versions per branch

CISA-ADP · OSV · NVD
Mio project mio
BranchAffectedFixed in
0.x≥ 0.7.2, < 0.8.110.8.11
0.x≥ 0.7.2, ≤ 0.8.10no fix published
Tokio
BranchAffectedFixed in
1.30+≥ 1.30.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • tokio-rs mio
    Affected
    • = >= 0.7.2, < 0.8.11no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-03-06

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bergWolfiall versions · fixed in 0.3.5-r2
  • bergChainguardall versions · fixed in 0.3.5-r2
  • cargo-auditWolfiall versions · fixed in 0.21.2-r1
  • cargo-auditChainguardall versions · fixed in 0.21.2-r1
  • kdashWolfiall versions · fixed in 0.6.1-r4
  • kdashChainguardall versions · fixed in 0.6.1-r4
  • linkerd-network-validatorWolfiall versions · fixed in 0.1.2-r2
  • linkerd-network-validatorChainguardall versions · fixed in 0.1.2-r2

10 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Mio project mio to 0.8.11

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2024-08-27
  • CNACVSS 3.17.5known since 2026-10-23
  • NVDCVSS 3.19.1read 2026-10-23
  • CNAweakness (CWE)CWE-416, CWE-672known since 2026-10-23
  • FIRST EPSSEPSS score0.9 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2024-03-04

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Published
2024-03-06
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-r8w9-5wcg-vfj7

Frequently asked questions

What is CVE-2024-27308?

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.

Is CVE-2024-27308 actively exploited?

A proof-of-concept exploit exists for CVE-2024-27308, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-27308?

CVE-2024-27308 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.

Running mio? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record