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 ws_stream_tungstenite

Dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-tungstenite^0.250.25.1up to date
 async_io_stream^0.30.3.3up to date
 bitflags^22.5.0up to date
 futures-core^0.30.3.30up to date
 futures-io^0.30.3.30up to date
 futures-sink^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 pharos^0.50.5.3up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.10.1.40up to date
 tungstenite^0.210.21.0up to date

Dev dependencies

(15 total, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^11.5.0up to date
 async-std^11.12.0up to date
 async-tungstenite^0.250.25.1up to date
 async_progress^0.20.2.1up to date
 asynchronous-codec^0.70.7.0up to date
 futures^0.30.3.30up to date
 futures-test^0.30.3.30up to date
 futures-timer^33.0.3up to date
 futures_ringbuf^0.40.4.0up to date
 pin-utils^0.10.1.0up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-util^0.70.7.11up to date
 tracing-log^0.20.2.0up to date
 tracing-subscriber^0.30.3.18up to date
 url^22.5.0up to date

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);