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, 11 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.102up to date
 bytes ⚠️^1.71.11.1maybe insecure
 derive_more^1.0.02.1.1out of date
 hickory-resolver=0.25.0-alpha.50.25.2out of date
 iroh-base^0.33.00.97.0out of date
 iroh-metrics^0.310.38.3out of date
 iroh-relay^0.330.97.0out of date
 n0-future^0.1.20.3.2out of date
 netwatch^0.30.15.0out of date
 portmapper^0.30.15.0out of date
 iroh-quinn^0.13.00.16.1out of date
 rand^0.80.10.0out of date
 reqwest^0.120.13.2out of date
 rustls ⚠️^0.230.23.37maybe insecure
 surge-ping^0.8.00.8.4up to date
 thiserror^22.0.18up to date
 tokio ⚠️^11.50.0maybe insecure
 tokio-util^0.7.120.7.18up to date
 tracing^0.10.1.44up to date
 url^2.42.5.8up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-lite^2.32.6.1up to date
 pretty_assertions^1.41.4.1up to date
 iroh-quinn^0.13.00.16.1out of date
 testresult^0.4.00.4.1up to date
 tokio ⚠️^11.50.0maybe insecure
 tracing-test^0.2.50.2.6up 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.

bytes: Integer overflow in `BytesMut::reserve`

RUSTSEC-2026-0007

In the unique reclaim path of BytesMut::reserve, the condition

if v_capacity >= new_cap + offset

uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

PoC

use bytes::*;

fn main() {
    let mut a = BytesMut::from(&b"hello world"[..]);
    let mut b = a.split_off(5);

    // Ensure b becomes the unique owner of the backing storage
    drop(a);

    // Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);

    // This call relies on the corrupted cap and may cause UB & HBO
    b.put_u8(b'h');
}

Workarounds

Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.