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 twilight-http

Dependencies

(19 total, 2 possibly insecure)

CrateRequiredLatestStatus
 brotli-decompressor^44.0.2up to date
 fastrand^22.3.0up to date
 http^11.3.1up to date
 http-body-util^0.10.1.3up to date
 hyper^11.6.0up to date
 hyper-hickory^0.70.7.0up to date
 hyper-rustls^0.27.30.27.5up to date
 hyper-tls^0.60.6.0up to date
 hyper-util^0.1.20.1.10up to date
 percent-encoding^22.3.1up to date
 rustls ⚠️^0.230.23.23maybe insecure
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 simd-json^0.14.0-rc.30.14.3up to date
 tokio ⚠️^1.01.44.1maybe insecure
 tracing^0.10.1.41up to date
 twilight-http-ratelimiting^0.16.00.16.0up to date
 twilight-model^0.16.00.16.0up to date
 twilight-validate^0.16.00.16.0up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 serde_test^11.0.177up to date
 static_assertions^1.1.01.1.0up to date
 tokio ⚠️^1.01.44.1maybe insecure
 twilight-util^0.16.00.16.0up 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.