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, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-tungstenite^0.220.28.0out of date
 async_io_stream^0.30.3.3up to date
 bitflags^22.6.0up to date
 futures-core^0.30.3.31up to date
 futures-io^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 log^0.40.4.22up to date
 pharos^0.50.5.3up to date
 tokio ⚠️^11.40.0maybe insecure
 tungstenite ⚠️^0.190.24.0out of date

Dev dependencies

(14 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^11.5.0up to date
 async-std^11.13.0up to date
 async-tungstenite^0.220.28.0out of date
 async_progress^0.20.2.1up to date
 asynchronous-codec^0.60.7.0out of date
 flexi_logger^0.250.29.1out of date
 futures^0.30.3.31up to date
 futures-test^0.30.3.31up to date
 futures-timer^33.0.3up to date
 futures_ringbuf^0.30.4.0out of date
 pin-utils^0.10.1.0up to date
 tokio ⚠️^11.40.0maybe insecure
 tokio-util^0.70.7.12up to date
 url^22.5.2up 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);

tungstenite: Tungstenite allows remote attackers to cause a denial of service

RUSTSEC-2023-0065

The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).