CVE-2023-22466

Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe

MEDIUM

5.4

CVSS Score

Published: January 4, 2023 at 09:47 PM UTC

Updated: June 17, 2026 at 05:35 AM UTC

2 products affected across 2 vendorsTokioTokio

Using tokio by tokio-rs?

Get instant alerts when new vulnerabilities affect tokio - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.4

Exploit prediction

EPSS 0.6%

SSVC

No known exploit

Description

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`.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tokio · Tokiocargo

95%

1.19.0 ≤ v < 1.20.31.21.0 ≤ v < 1.23.11.7.0 ≤ v < 1.18.4

Affected range stops below 1.18.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.20.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.23.1, so it looks safe — our inference, not a vendor statement

Tokio · Tokio Rs

60%

v < 1.18.4v < 1.20.3v < 1.23.1

Affected range stops below 1.18.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.20.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.23.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tokio-rs/tokio/pull/5336

x_refsource_MISCRelease NotesThird Party Advisory

Source: [email protected]

https://github.com/tokio-rs/tokio/releases/tag/tokio-1.23.1

x_refsource_CONFIRMMitigationThird Party Advisory

Source: [email protected]

https://github.com/tokio-rs/tokio/security/advisories/GHSA-7rrj-xr53-82p7

x_refsource_MISCTechnical DescriptionThird Party Advisory

Source: [email protected]

https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea#pipe_reject_remote_clients

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.4MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: NONE
Availability: LOW

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-665

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card