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 quickie

Dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 bytes^11.7.2up to date
 futures-util^0.30.3.31up to date
 parking_lot^0.120.12.3up to date
 quinn^0.110.11.5up to date
 quinn-proto ⚠️^0.110.11.8maybe insecure
 tokio^1.241.40.0up to date
 tokio-util^0.70.7.12up to date
 tracing^0.10.1.40up to date

Dev dependencies

(10 total, all up-to-date)

CrateRequiredLatestStatus
 deadline^0.20.2.0up to date
 humansize^22.1.3up to date
 libp2p^0.540.54.1up to date
 libp2p-tls^0.50.5.0up to date
 libp2p-quic^0.110.11.1up to date
 peak_alloc^0.20.2.1up to date
 rcgen^0.130.13.1up to date
 rustls^0.23.120.23.14up to date
 tokio^1.241.40.0up to date
 tracing-subscriber^0.30.3.18up to date

Security Vulnerabilities

quinn-proto: `Endpoint::retry()` calls can lead to panicking

RUSTSEC-2024-0373

In 0.11.0, we overhauled the server-side Endpoint implementation to enable more careful handling of incoming connection attempts. However, some of the code paths that cleaned up state after connection attempts were processed confused the initial destination connection ID with the destination connection ID of a substantial package. This resulted in the internal Endpoint state becoming inconsistent, which could then lead to a panic.

https://github.com/quinn-rs/quinn/commit/e01609ccd8738bd438d86fa7185a0f85598cb58f

Thanks to @finbear for reporting and investingating, and to @BiagoFesta for coordinating.