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

Dependencies

(12 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.0.11.3.2up to date
 bytes^11.6.0up to date
 rand^0.80.8.5up to date
 ring^0.16.70.17.8out of date
 rustc-hash^1.11.1.0up to date
 rustls ⚠️^0.20.40.23.9out of date
 rustls-native-certs^0.60.7.0out of date
 slab^0.40.4.9up to date
 thiserror^1.0.211.0.61up to date
 tinyvec^1.11.6.0up to date
 tracing^0.1.100.1.40up to date
 webpki ⚠️^0.220.22.4maybe insecure

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 assert_matches^1.11.5.0up to date
 hex-literal^0.3.00.4.1out of date
 lazy_static^11.4.0up to date
 rcgen^0.10.00.13.1out of date
 tracing-subscriber^0.3.00.3.18up to date

Security Vulnerabilities

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If 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.