Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.18.4, 1.20.3, 1.23.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Tokio is a runtime for writing applications with Rust. Starting with version 1.7.0 and prior to versions 1.18.4, 1.20.3, and 1.23.1, when configuring a Windows named pipe server, setting `pipe_mode` will reset `reject_remote_clients` to `false`. If the application has previously configured `reject_remote_clients` to `true`, this effectively undoes the configuration. Remote clients may only access the named pipe if the named pipe's associated path is accessible via a publicly shared folder (SMB). Versions 1.23.1, 1.20.3, and 1.18.4 have been patched. The fix will also be present in all releases starting from version 1.24.0. Named pipes were introduced to Tokio in version 1.7.0, so releases older than 1.7.0 are not affected. As a workaround, ensure that `pipe_mode` is set first after initializing a `ServerOptions`.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tokio-rs tokio
From 1.7.0 · fixed in 1.18.4; From 1.19.0 · fixed in 1.20.3; From 1.21.0 · fixed in 1.23.1
- tokiocrates.io
From 1.7.0 · fixed in 1.18.4; From 1.19.0 · fixed in 1.20.3; From 1.21.0 · fixed in 1.23.1
- tokiocrates.io
From 1.7.0 · fixed in 1.18.4
- tokiocrates.io
From 1.19.0 · fixed in 1.20.3
- tokiocrates.io
From 1.21.0 · fixed in 1.23.1