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, 32 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 axum^0.7.40.8.4out of date
 backoff^0.4.00.4.0up to date
 base64^0.22.10.22.1up to date
 bytes^1.71.10.1up to date
 clap^44.5.40up to date
 der^0.70.7.10up to date
 derive_more^1.0.02.0.1out of date
 futures-buffered^0.2.80.2.11up to date
 futures-concurrency^7.6.07.6.3up 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.10.0out of date
 hex^0.4.30.4.3up to date
 hickory-proto ⚠️=0.25.0-alpha.20.25.2out of date
 hickory-resolver=0.25.0-alpha.20.25.2out of date
 hostname^0.3.10.4.1out of 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.14up to date
 igd-next^0.15.10.16.1out of date
 iroh-base^0.28.00.90.0out of date
 iroh-metrics^0.28.00.35.0out of date
 libc^0.2.1390.2.174up to date
 netdev^0.30.00.36.0out of date
 netlink-packet-core^0.7.00.7.0up to date
 netlink-packet-route^0.17.00.24.0out of date
 netlink-sys^0.8.50.8.7up to date
 netwatch^0.1.00.6.0out of date
 num_enum^0.70.7.4up to date
 once_cell^1.18.01.21.3up to date
 parking_lot^0.12.10.12.4up to date
 pin-project^11.1.10up to date
 pkarr^23.8.0out of date
 portmapper^0.1.00.6.1out of date
 postcard^11.1.2up to date
 iroh-quinn^0.12.00.14.0out of date
 iroh-quinn-proto^0.12.00.13.0out of date
 iroh-quinn-udp^0.5.50.5.7up to date
 rand^0.80.9.1out of date
 rcgen^0.120.14.1out of date
 regex^1.7.11.11.1up to date
 reqwest^0.120.12.22up to date
 ring ⚠️^0.170.17.14maybe insecure
 rtnetlink^0.13.00.17.0out of date
 rustls ⚠️^0.230.23.28maybe insecure
 rustls-pemfile^2.12.2.0up to date
 serde^11.0.219up to date
 smallvec^1.11.11.15.1up to date
 socket2^0.5.30.6.0out of date
 strum^0.26.20.27.1out of date
 stun-rs^0.1.50.1.11up to date
 surge-ping^0.8.00.8.2up to date
 swarm-discovery^0.2.10.4.0out of date
 thiserror^12.0.12out of date
 time^0.3.200.3.41up to date
 tokio ⚠️^11.46.1maybe insecure
 tokio-rustls^0.260.26.2up to date
 tokio-rustls-acme^0.40.7.1out of date
 tokio-stream^0.1.150.1.17up to date
 tokio-tungstenite^0.210.27.0out of date
 tokio-tungstenite-wasm^0.30.6.0out of date
 tokio-util^0.7.120.7.15up to date
 toml^0.80.8.23up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 tungstenite^0.210.27.0out of date
 url^2.42.5.4up to date
 watchable^1.1.21.1.2up to date
 rustls-webpki^0.1020.103.3out of date
 webpki-roots^0.261.0.1out of date
 windows^0.510.61.3out of date
 wmi^0.130.17.2out of date
 x509-parser^0.160.17.0out of date
 z32^1.0.31.3.0up to date

Dev dependencies

(14 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.7.40.8.4out of date
 clap^44.5.40up to date
 criterion^0.5.10.6.0out of date
 crypto_box^0.9.10.9.1up to date
 iroh-test^0.28.00.31.0out of date
 mainline^2.0.15.4.0out of date
 ntest^0.90.9.3up to date
 pretty_assertions^1.41.4.1up to date
 proptest^1.2.01.7.0up to date
 rand_chacha^0.3.10.9.0out of date
 serde_json^1.0.1071.0.140up to date
 testresult^0.4.00.4.1up to date
 tokio ⚠️^11.46.1maybe 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.

hickory-proto: Hickory DNS failure to verify self-signed RRSIG for DNSKEYs

RUSTSEC-2025-0006

Summary

The DNSSEC validation routines treat entire RRsets of DNSKEY records as trusted once they have established trust in only one of the DNSKEYs. As a result, if a zone includes a DNSKEY with a public key that matches a configured trust anchor, all keys in that zone will be trusted to authenticate other records in the zone. There is a second variant of this vulnerability involving DS records, where an authenticated DS record covering one DNSKEY leads to trust in signatures made by an unrelated DNSKEY in the same zone.

Details

verify_dnskey_rrset() will return Ok(true) if any record's public key matches a trust anchor. This results in verify_rrset() returning a Secure proof. This ultimately results in successfully verifying a response containing DNSKEY records. verify_default_rrset() looks up DNSKEY records by calling handle.lookup(), which takes the above code path. There's a comment following this that says "DNSKEYs were already validated by the inner query in the above lookup", but this is not the case. To fully verify the whole RRset of DNSKEYs, it would be necessary to check self-signatures by the trusted key over the other keys. Later in verify_default_rrset(), verify_rrset_with_dnskey() is called multiple times with different keys and signatures, and if any call succeeds, then its Proof is returned.

Similarly, verify_dnskey_rrset() returns Ok(false) if any DNSKEY record is covered by a DS record. A comment says "If all the keys are valid, then we are secure", but this is only checking that one key is authenticated by a DS in the parent zone's delegation point. This time, after control flow returns to verify_rrset(), it will call verify_default_rrset(). The special handling for DNSKEYs in verify_default_rrset() will then call verify_rrset_with_dnskey() using each KSK DNSKEY record, and if one call succeeds, return its Proof. If there are multiple KSK DNSKEYs in the RRset, then this leads to another authentication break. We need to either pass the authenticated DNSKEYs from the DS covering check to the RRSIG validation, or we need to perform this RRSIG validation of the DNSKEY RRset inside verify_dnskey_rrset() and cut verify_default_rrset() out of DNSKEY RRset validation entirely.

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.