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 quic-rpc

Dependencies

(23 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 bytes^11.10.1up to date
 document-features^0.20.2.11up to date
 flume^0.110.11.1up to date
 futures^0.3.300.3.31up to date
 futures-lite^2.3.02.6.0up to date
 futures-sink^0.3.300.3.31up to date
 futures-util^0.3.300.3.31up to date
 hyper^0.14.161.6.0out of date
 iroh^0.330.33.0up to date
 pin-project^11.1.10up to date
 postcard^11.1.1up to date
 iroh-quinn^0.130.13.0up to date
 rcgen^0.130.13.2up to date
 rustls ⚠️^0.230.23.23maybe insecure
 serde^11.0.219up to date
 slab^0.4.90.4.9up to date
 smallvec^1.13.21.14.0up to date
 time^0.3.360.3.39up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-serde^0.90.9.0up to date
 tokio-util^0.70.7.14up to date
 tracing^0.10.1.41up to date

Dev dependencies

(16 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 async-stream^0.3.30.3.6up to date
 derive_more^12.0.1out of date
 futures-buffered^0.2.40.2.11up to date
 nested_enum_utils^0.1.00.1.0up to date
 proc-macro2^1.0.661.0.94up to date
 iroh-quinn^0.130.13.0up to date
 rand^0.80.9.0out of date
 rcgen^0.130.13.2up to date
 serde^11.0.219up to date
 tempfile^3.5.03.19.0up to date
 testresult^0.4.10.4.1up to date
 thousands^0.2.00.2.0up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-util^0.70.7.14up to date
 tracing-subscriber^0.3.160.3.19up 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.