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 iroh-relay

Dependencies

(50 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 bytes^1.71.10.1up to date
 clap^44.5.32up to date
 dashmap^6.1.06.1.0up to date
 data-encoding^2.6.02.8.0up to date
 derive_more^1.0.02.0.1out of date
 governor^0.7.00.8.1out of date
 hickory-proto=0.25.0-alpha.50.24.4up to date
 hickory-resolver=0.25.0-alpha.50.24.4up to date
 http^11.3.1up to date
 http-body-util^0.1.00.1.3up to date
 hyper^11.6.0up to date
 hyper-util^0.1.10.1.10up to date
 iroh-base^0.33.00.33.0up to date
 iroh-metrics^0.310.32.0out of date
 lru^0.120.13.0out of date
 n0-future^0.1.20.1.2up to date
 num_enum^0.70.7.3up to date
 pin-project^11.1.10up to date
 pkarr^23.6.0out of date
 postcard^11.1.1up to date
 iroh-quinn^0.13.00.13.0up to date
 iroh-quinn-proto^0.13.00.13.0up to date
 rand^0.80.9.0out of date
 rcgen^0.130.13.2up to date
 regex^1.7.11.11.1up to date
 reloadable-state^0.10.1.0up to date
 reqwest^0.120.12.14up to date
 rustls ⚠️^0.230.23.23maybe insecure
 rustls-cert-file-reader^0.4.10.4.1up to date
 rustls-cert-reloadable-resolver^0.7.10.7.1up to date
 rustls-pemfile^2.12.2.0up to date
 serde^11.0.219up to date
 strum^0.260.27.1out of date
 stun-rs^0.1.50.1.10up to date
 thiserror^22.0.12up to date
 time^0.3.370.3.39up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-rustls^0.260.26.2up to date
 tokio-rustls-acme^0.60.6.0up to date
 tokio-tungstenite^0.240.26.2out of date
 tokio-tungstenite-wasm^0.40.5.0out of date
 tokio-util^0.70.7.14up to date
 toml^0.80.8.20up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 url^2.52.5.4up to date
 rustls-webpki^0.1020.103.0out of date
 webpki-roots^0.260.26.8up to date
 z32^1.0.31.3.0up to date

Dev dependencies

(9 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^44.5.32up to date
 crypto_box^0.9.10.9.1up to date
 proptest^1.2.01.6.0up to date
 rand_chacha^0.3.10.9.0out of date
 serde_json^11.0.140up to date
 testresult^0.4.00.4.1up to date
 tokio ⚠️^11.44.1maybe insecure
 tracing-subscriber^0.30.3.19up to date
 tracing-test^0.2.50.2.5up 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.