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 utsuru

Dependencies

(21 total, 2 possibly insecure)

CrateRequiredLatestStatus
 axum^0.80.8.4up to date
 bytes^11.10.1up to date
 clap^4.54.5.40up to date
 clap_complete^4.54.5.54up to date
 futures-util^0.30.3.31up to date
 http^11.3.1up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.3up to date
 rand^0.90.9.1up to date
 rustls ⚠️^0.230.23.28maybe insecure
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-websockets^0.110.11.4up to date
 tower^0.50.5.2up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 twilight-gateway^0.160.16.0up to date
 twilight-model^0.160.16.0up to date
 uuid^11.17.0up to date
 webrtc^0.130.13.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.