This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate async-wsocket

Dependencies

(15 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arti-client^0.280.39.0out of date
 async-utility^0.30.3.1up to date
 futures^0.30.3.32up to date
 futures-util^0.30.3.32up to date
 js-sys^0.30.3.87up to date
 tokio ⚠️^11.49.0maybe insecure
 tokio-rustls^0.260.26.4up to date
 tokio-socks^0.50.5.2up to date
 tokio-tungstenite^0.260.28.0out of date
 tor-hsrproxy^0.280.39.0out of date
 tor-hsservice^0.280.39.0out of date
 tor-rtcompat^0.280.39.0out of date
 url^2.52.5.8up to date
 wasm-bindgen^0.20.2.110up to date
 web-sys^0.30.3.87up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.49.0maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);