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

Dependencies

(17 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-executor^1.13.01.13.1up to date
 async-fs^2.12.1.2up to date
 async-global-executor^2.4.12.4.1up to date
 async-io^22.4.0up to date
 async-std^1.121.13.0up to date
 bytes^11.9.0up to date
 futures-io^0.3.190.3.31up to date
 pin-project-lite^0.20.2.16up to date
 iroh-quinn-proto^0.12.00.12.0up to date
 rustc-hash^22.1.0up to date
 rustls ⚠️^0.23.50.23.21maybe insecure
 smol^22.0.2up to date
 socket2^0.50.5.8up to date
 thiserror^1.0.212.0.11out of date
 tokio^1.28.11.43.0up to date
 tracing^0.1.100.1.41up to date
 iroh-quinn-udp^0.50.5.5up to date

Dev dependencies

(13 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.95up to date
 bencher^0.1.50.1.5up to date
 clap^4.54.5.27up to date
 crc^33.2.1up to date
 directories-next^22.0.0up to date
 rand^0.80.9.0out of date
 rcgen^0.130.13.2up to date
 rustls-pemfile^22.2.0up to date
 tokio^1.28.11.43.0up to date
 tokio-stream^0.1.150.1.17up to date
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber^0.3.10.3.19up to date
 url^22.5.4up to date

Security Vulnerabilities

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.