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 broadcastr

Dependencies

(27 total, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.102up to date
 argh^0.10.1.19up to date
 backon^11.6.0up to date
 const_format^0.20.2.36up to date
 futures^0.30.3.32up to date
 futures-util^0.30.3.32up to date
 git-version^0.30.3.9up to date
 governor^0.100.10.4up to date
 http-body-util^0.10.1.3up to date
 http_wire^0.70.7.1up to date
 humantime^22.3.0up to date
 indexmap^22.14.0up to date
 itertools^0.140.14.0up to date
 json-patch^44.2.0up to date
 log^0.40.4.30up to date
 lru^0.180.18.0up to date
 mime^0.30.3.17up to date
 nonzero_ext^0.30.3.0up to date
 parking_lot^0.120.12.5up to date
 reqwest^0.130.13.4up to date
 rustls ⚠️^0.230.23.40maybe insecure
 simplelog^0.120.12.2up to date
 socket2^0.60.6.4up to date
 tokio ⚠️^11.52.3maybe insecure
 tokio-graceful-shutdown^0.190.19.3up to date
 tokio-tungstenite^0.290.29.0up to date
 tungstenite^0.290.29.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.