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

Dependencies

(20 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 bytes^1.71.10.1up to date
 derive_more^1.0.02.0.1out of date
 hickory-resolver=0.25.0-alpha.50.24.4up to date
 iroh-base^0.33.00.33.0up to date
 iroh-metrics^0.310.32.0out of date
 iroh-relay^0.330.33.0up to date
 n0-future^0.1.20.1.2up to date
 netwatch^0.30.4.0out of date
 portmapper^0.30.4.0out of date
 iroh-quinn^0.13.00.13.0up to date
 rand^0.80.9.0out of date
 reqwest^0.120.12.14up to date
 rustls ⚠️^0.230.23.23maybe insecure
 surge-ping^0.8.00.8.2up to date
 thiserror^22.0.12up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-util^0.7.120.7.14up to date
 tracing^0.10.1.41up to date
 url^2.42.5.4up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-lite^2.32.6.0up to date
 pretty_assertions^1.41.4.1up to date
 iroh-quinn^0.13.00.13.0up to date
 testresult^0.4.00.4.1up to date
 tokio ⚠️^11.44.1maybe insecure
 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.