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 hyper-tungstenite

Dependencies

(7 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 http-body-util^0.1.00.1.2up to date
 hyper^1.0.01.5.0up to date
 hyper-util^0.1.00.1.10up to date
 pin-project-lite^0.2.100.2.15up to date
 tokio ⚠️^1.2.01.41.0maybe insecure
 tokio-tungstenite^0.21.00.24.0out of date
 tungstenite^0.21.00.24.0out of date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 assert2^0.3.40.3.15up to date
 futures^0.3.120.3.31up to date
 hyper^1.0.01.5.0up to date
 tokio ⚠️^1.2.01.41.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);