{"id":"GHSA-7rrj-xr53-82p7","revision":"854c64fd28814619a385bcc9b8ca2be2","records":[{"revision":"854c64fd28814619a385bcc9b8ca2be2","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-7rrj-xr53-82p7","aliases":["CVE-2023-22466","RUSTSEC-2023-0001"],"title":"Tokio reject_remote_clients configuration may get dropped when creating a Windows named pipe","description":"### Impact\n\nWhen 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. This also applies if `reject_remote_clients` is not explicitly set as this is the default configuration and is cleared by calling `pipe_mode`.\n\nRemote clients may only access the named pipe if the named pipe's associated path is accessible via a publically shared folder (SMB).\n\n### Patches\n\nThe following versions have been patched:\n* 1.23.1\n* 1.20.3\n* 1.18.4\n\nThe fix will also be present in all releases starting from version 1.24.0.\n\nNamed pipes were introduced to Tokio in version 1.7.0, so releases older than 1.7.0 are not affected.\n\n### Workarounds\n\nEnsure that `pipe_mode` is set **first** after initializing a `ServerOptions`. For example:\n\n```rust\nlet mut opts = ServerOptions::new();\nopts.pipe_mode(PipeMode::Message);\nopts.reject_remote_clients(true);\n```\n\n### References\n\nhttps://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients\n","state":0,"publishedAt":"2023-01-06T21:40:58+00:00","modifiedAt":"2026-09-10T03:49:51.032327+00:00","affected":[{"ecosystem":"crates.io","name":"tokio","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"1.7.0"},{"kind":"fixed","version":"1.18.4"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"tokio","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"1.19.0"},{"kind":"fixed","version":"1.20.3"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"tokio","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"1.21.0"},{"kind":"fixed","version":"1.23.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/tokio-rs/tokio/security/advisories/GHSA-7rrj-xr53-82p7","https://nvd.nist.gov/vuln/detail/CVE-2023-22466","https://github.com/tokio-rs/tokio/pull/5336","https://github.com/tokio-rs/tokio","https://github.com/tokio-rs/tokio/releases/tag/tokio-1.23.1","https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients","https://rustsec.org/advisories/RUSTSEC-2023-0001.html"],"sourceUrl":"https://github.com/advisories/GHSA-7rrj-xr53-82p7","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-7rrj-xr53-82p7","identifiers":["GHSA-7rrj-xr53-82p7","CVE-2023-22466","RUSTSEC-2023-0001"]},"retained":false,"historicalAffected":[]}],"coverage":[]}