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`.
References
Link | Resource |
---|---|
https://github.com/tokio-rs/tokio/pull/5336 | Patch Third Party Advisory |
https://github.com/tokio-rs/tokio/releases/tag/tokio-1.23.1 | Release Notes Third Party Advisory |
https://github.com/tokio-rs/tokio/security/advisories/GHSA-7rrj-xr53-82p7 | Mitigation Third Party Advisory |
https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients | Technical Description Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: GitHub_M
Published: 2023-01-04T21:47:09.400Z
Updated:
Reserved: 2022-12-29T03:00:40.879Z
Link: CVE-2023-22466
JSON object: View
NVD Information
Status : Analyzed
Published: 2023-01-04T22:15:09.267
Modified: 2023-01-11T02:09:46.390
Link: CVE-2023-22466
JSON object: View
Redhat Information
No data.
CWE