CVE-2023-22466 json
Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe
published 3y ago modified last mo. also GHSA-7rrj-xr53-82p7 , RUSTSEC-2023-0001 , EUVD-2023-0393
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
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`.
Patch / fix
- crates.io tokio 1.18.4, 1.20.3, 1.23.1
- tokio tokio 1.18.4, 1.20.3, 1.23.1
- rust-tokio Debian 14, Debian 13, Debian 12 1.24.2-1
debian advisories DEBIAN-CVE-2023-22466
- github.com/tokio-rs/tokio#5336 pull request
- github.com/tokio-rs/tokio/releases/tag/tokio-1.23.1 release
Is CVE-2023-22466 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | tokio | >=1.7.0, <1.18.4 >=1.19.0, <1.20.3 >=1.21.0, <1.23.1 |
1.18.4 1.20.3 1.23.1 |
Affected products
- tokio-rs tokio
Classification
- Weakness
-
- CWE-665 Improper Initialization
References
-
github.com
/tokio-rs/tokio/pull/5336
web, patch, third-party-advisory
-
github.com
/tokio-rs/tokio/security/advisories/GHSA-7rrj-xr53-82p7
web, mitigation, third-party-advisory
-
github.com
/tokio-rs/tokio/releases/tag/tokio-1.23.1
web, release-notes, third-party-advisory
-
learn.microsoft.com
/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients
web, technical-description, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-22466
advisory
-
github.com
/tokio-rs/tokio
package
-
rustsec.org
/advisories/RUSTSEC-2023-0001.html
web, advisory
-
crates.io
/crates/tokio
package
Sources
- CVE List CVE-2023-22466
- GitHub Advisory GHSA-7rrj-xr53-82p7
- NVD CVE-2023-22466
- OSV RUSTSEC-2023-0001
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.