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 tokio-tungstenite-wasm

Dependencies

(12 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 futures-channel^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 http^11.3.1up to date
 httparse^11.10.1up to date
 js-sys^0.30.3.77up to date
 native-tls^0.20.2.14up to date
 rustls ⚠️^0.230.23.23maybe insecure
 thiserror^12.0.12out of date
 tokio ⚠️^11.44.1maybe insecure
 tokio-tungstenite^0.240.26.2out of date
 wasm-bindgen^0.20.2.100up to date
 web-sys^0.30.3.77up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert-impl^0.10.1.3up to date
 rand^0.80.9.0out of date
 tokio ⚠️^11.44.1maybe 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);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.