Improper Initialization Affecting rust-tokio package, versions <1.24.2-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.1% (28th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN12-RUSTTOKIO-3227604
  • published10 Jan 2023
  • disclosed4 Jan 2023

Introduced: 4 Jan 2023

CVE-2023-22466  (opens in a new tab)
CWE-665  (opens in a new tab)

How to fix?

Upgrade Debian:12 rust-tokio to version 1.24.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-tokio package and not the rust-tokio package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1