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 volo

Dependencies

(22 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-broadcast^0.60.7.2out of date
 dashmap^56.1.0out of date
 faststr^0.20.2.31up to date
 futures^0.30.3.31up to date
 lazy_static^11.5.0up to date
 libc^0.20.2.174up to date
 rustls ⚠️^0.220.23.28out of date
 metainfo^0.70.7.14up to date
 motore^0.40.4.1up to date
 mur3^0.10.1.0up to date
 nix^0.270.30.1out of date
 once_cell^11.21.3up to date
 pin-project^11.1.10up to date
 rand^0.80.9.1out of date
 socket2^0.50.6.0out of date
 thiserror^12.0.12out of date
 tokio ⚠️^11.46.1maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.250.26.2out of date
 tokio-stream^0.10.1.17up to date
 tower^0.40.5.2out of date
 tracing^0.10.1.41up 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::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.