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 alloy-transport-ws

Dependencies

(10 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 alloy-pubsub^0.60.8.1out of date
 alloy-transport^0.60.8.1out of date
 futures^0.30.3.31up to date
 http^1.11.2.0up to date
 rustls ⚠️^0.230.23.20maybe insecure
 serde_json^1.01.0.133up to date
 tokio ⚠️^11.42.0maybe insecure
 tokio-tungstenite^0.240.26.0out of date
 tracing^0.10.1.41up to date
 ws_stream_wasm^0.7.40.7.4up 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);

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.