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 vndb

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 rustls ⚠️^0.230.23.16maybe insecure
 serde^11.0.214up to date
 serde_json^11.0.132up to date
 tokio^1.281.41.0up to date
 tokio-rustls^0.260.26.0up to date
 webpki-roots^0.260.26.6up to date

Dev dependencies

(2 total, 2 possibly insecure)

CrateRequiredLatestStatus
 rustls ⚠️^0.230.23.16maybe insecure
 tokio ⚠️^1.01.41.0maybe 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::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.