Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe
Résumé
Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe
Description d'origine
La description telle que publiée par la source (souvent en anglais).
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Paquets affectés
État des correctifs par distribution
Paquets corrigés publiés par chaque distribution pour cette CVE
- Debian DEBIAN-CVE-2023-22466 rust-tokio Corrigé dans: 1.24.2-1
Références
- advisory github.com
- advisory nvd.nist.gov
- advisory rustsec.org
- advisory github.com
- package github.com
- package crates.io
- patch github.com
- web github.com
- web learn.microsoft.com