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.36maybe insecure
 serde^11.0.228up to date
 serde_json^11.0.148up to date
 tokio^1.281.49.0up to date
 tokio-rustls^0.260.26.4up to date
 webpki-roots^11.0.5up to date

Dev dependencies

(2 total, 2 possibly insecure)

CrateRequiredLatestStatus
 rustls ⚠️^0.230.23.36maybe insecure
 tokio ⚠️^1.01.49.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 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.