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.
quinn(13 total, 1 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-io | ^2.0 | 2.3.4 | up to date |
| async-std | ^1.11 | 1.13.0 | up to date |
| bytes | ^1 | 1.7.2 | up to date |
| futures-io | ^0.3.19 | 0.3.31 | up to date |
| pin-project-lite | ^0.2 | 0.2.14 | up to date |
| quinn-proto ⚠️ | ^0.11.2 | 0.11.8 | maybe insecure |
| rustc-hash | ^1.1 | 2.0.0 | out of date |
| rustls ⚠️ | ^0.23 | 0.23.15 | maybe insecure |
| smol | ^2 | 2.0.2 | up to date |
| thiserror | ^1.0.21 | 1.0.64 | up to date |
| tokio | ^1.28.1 | 1.40.0 | up to date |
| tracing | ^0.1.10 | 0.1.40 | up to date |
| quinn-udp | ^0.5 | 0.5.5 | up to date |
(12 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.22 | 1.0.89 | up to date |
| bencher | ^0.1.5 | 0.1.5 | up to date |
| clap | ^4 | 4.5.20 | up to date |
| crc | ^3 | 3.2.1 | up to date |
| directories-next | ^2 | 2.0.0 | up to date |
| rand | ^0.8 | 0.8.5 | up to date |
| rcgen | ^0.13 | 0.13.1 | up to date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| tokio | ^1.28.1 | 1.40.0 | up to date |
| tracing-futures | ^0.2.0 | 0.2.5 | up to date |
| tracing-subscriber | ^0.3.0 | 0.3.18 | up to date |
| url | ^2 | 2.5.2 | up to date |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
quinn-proto: `Endpoint::retry()` calls can lead to panickingIn 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.