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

Dependencies

(56 total, 13 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 aead^0.5.20.5.2up to date
 anyhow^11.0.97up to date
 atomic-waker^1.1.21.1.2up to date
 axum^0.70.8.1out of date
 backoff^0.4.00.4.0up to date
 bytes^1.71.10.1up to date
 clap^44.5.32up to date
 concurrent-queue^2.52.5.0up to date
 crypto_box^0.9.10.9.1up to date
 data-encoding^2.22.8.0up to date
 der^0.70.7.9up to date
 derive_more^1.0.02.0.1out of date
 ed25519-dalek^2.02.1.1up to date
 futures-util^0.30.3.31up to date
 hickory-resolver=0.25.0-alpha.50.24.4up to date
 http^11.3.1up to date
 igd-next^0.15.10.16.0out of date
 indicatif^0.170.17.11up to date
 instant^0.10.1.13up 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
 iroh-net-report^0.330.33.0up to date
 netdev^0.31.00.33.0out of date
 netwatch^0.30.4.0out of date
 parse-size=1.0.01.1.0out of date
 pin-project^11.1.10up to date
 pkarr^23.6.0out of date
 portmapper^0.30.4.0out of date
 iroh-quinn^0.13.00.13.0up to date
 iroh-quinn-proto^0.13.00.13.0up to date
 iroh-quinn-udp^0.5.70.5.7up to date
 rand^0.80.9.0out of date
 rcgen^0.130.13.2up to date
 reqwest^0.120.12.14up to date
 ring ⚠️^0.170.17.14maybe insecure
 rustls ⚠️^0.230.23.23maybe insecure
 serde^11.0.219up to date
 smallvec^1.11.11.14.0up to date
 strum^0.260.27.1out of date
 stun-rs^0.1.50.1.10up to date
 swarm-discovery^0.3.0-alpha.20.2.1up to date
 thiserror^22.0.12up to date
 time^0.30.3.39up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-stream^0.1.150.1.17up to date
 tokio-util^0.70.7.14up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 url^2.52.5.4up to date
 wasm-bindgen-futures^0.40.4.50up to date
 rustls-webpki^0.1020.103.0out of date
 webpki-roots^0.260.26.8up to date
 x509-parser^0.160.17.0out of date
 z32^1.0.31.3.0up to date

Dev dependencies

(12 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.70.8.1out of date
 clap^44.5.32up to date
 futures-lite^2.62.6.0up to date
 pretty_assertions^1.41.4.1up 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-subscriber-wasm^0.1.00.1.0up to date
 tracing-test^0.2.50.2.5up to date
 wasm-bindgen-test^0.30.3.50up 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.

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.