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-net

Dependencies

(78 total, 20 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.95up to date
 axum^0.7.40.8.1out of date
 backoff^0.4.00.4.0up to date
 base64^0.22.10.22.1up to date
 bytes^1.71.9.0up to date
 clap^44.5.27up to date
 der^0.70.7.9up to date
 derive_more^1.0.01.0.0up to date
 futures-buffered^0.2.80.2.9up to date
 futures-concurrency^7.6.07.6.2up to date
 futures-lite^2.32.6.0up to date
 futures-sink^0.3.250.3.31up to date
 futures-util^0.3.250.3.31up to date
 genawaiter^0.99.10.99.1up to date
 governor^0.6.00.8.0out of date
 hex^0.4.30.4.3up to date
 hickory-proto=0.25.0-alpha.20.24.2up to date
 hickory-resolver=0.25.0-alpha.20.24.2up to date
 hostname^0.3.10.4.0out of date
 http^11.2.0up to date
 http-body-util^0.1.00.1.2up to date
 hyper^11.5.2up to date
 hyper-util^0.1.10.1.10up to date
 igd-next^0.15.10.16.0out of date
 iroh-base^0.28.00.31.0out of date
 iroh-metrics^0.28.00.31.0out of date
 libc^0.2.1390.2.169up to date
 netdev^0.30.00.32.0out of date
 netlink-packet-core^0.7.00.7.0up to date
 netlink-packet-route^0.17.00.21.0out of date
 netlink-sys^0.8.50.8.7up to date
 netwatch^0.1.00.3.0out of date
 num_enum^0.70.7.3up to date
 once_cell^1.18.01.20.2up to date
 parking_lot^0.12.10.12.3up to date
 pin-project^11.1.8up to date
 pkarr^22.3.1up to date
 portmapper^0.1.00.3.1out of date
 postcard^11.1.1up to date
 iroh-quinn^0.12.00.12.0up to date
 iroh-quinn-proto^0.12.00.12.0up to date
 iroh-quinn-udp^0.5.50.5.5up to date
 rand^0.80.9.0out of date
 rcgen^0.120.13.2out of date
 regex^1.7.11.11.1up to date
 reqwest^0.120.12.12up to date
 ring^0.170.17.8up to date
 rtnetlink^0.13.00.14.1out of date
 rustls ⚠️^0.230.23.21maybe insecure
 rustls-pemfile^2.12.2.0up to date
 serde^11.0.217up to date
 smallvec^1.11.11.13.2up to date
 socket2^0.5.30.5.8up to date
 strum^0.26.20.26.3up to date
 stun-rs^0.1.50.1.9up to date
 surge-ping^0.8.00.8.1up to date
 swarm-discovery^0.2.10.2.1up to date
 thiserror^12.0.11out of date
 time^0.3.200.3.37up to date
 tokio ⚠️^11.43.0maybe insecure
 tokio-rustls^0.260.26.1up to date
 tokio-rustls-acme^0.40.6.0out of date
 tokio-stream^0.1.150.1.17up to date
 tokio-tungstenite^0.210.26.1out of date
 tokio-tungstenite-wasm^0.30.4.0out of date
 tokio-util^0.7.120.7.13up to date
 toml^0.80.8.19up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 tungstenite^0.210.26.1out of date
 url^2.42.5.4up to date
 watchable^1.1.21.1.2up to date
 rustls-webpki^0.1020.102.8up to date
 webpki-roots^0.260.26.7up to date
 windows^0.510.59.0out of date
 wmi^0.130.14.4out of date
 x509-parser^0.160.16.0up to date
 z32^1.0.31.1.1up to date

Dev dependencies

(14 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.7.40.8.1out of date
 clap^44.5.27up to date
 criterion^0.5.10.5.1up to date
 crypto_box^0.9.10.9.1up to date
 iroh-test^0.28.00.31.0out of date
 mainline^2.0.14.2.1out of date
 ntest^0.90.9.3up to date
 pretty_assertions^1.41.4.1up to date
 proptest^1.2.01.6.0up to date
 rand_chacha^0.3.10.9.0out of date
 serde_json^1.0.1071.0.137up to date
 testresult^0.4.00.4.1up to date
 tokio ⚠️^11.43.0maybe insecure
 tracing-subscriber^0.30.3.19up 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.