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 zenoh-link-commons

Dependencies

(26 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.820.1.89up to date
 base64^0.22.10.22.1up to date
 flume^0.110.11.1up to date
 futures^0.3.310.3.31up to date
 quinn^0.11.50.11.8up to date
 rustls ⚠️^0.23.130.23.31maybe insecure
 rustls-pemfile^2.1.32.2.0up to date
 rustls-pki-types^1.8.01.12.0up to date
 rustls-webpki^0.102.80.103.4out of date
 secrecy^0.8.00.10.3out of date
 serde^1.0.2101.0.219up to date
 socket2^0.5.70.6.0out of date
 time^0.3.360.3.41up to date
 tokio^1.40.01.47.1up to date
 tokio-util^0.7.120.7.16up to date
 tracing^0.10.1.41up to date
 webpki-roots^0.26.51.0.2out of date
 x509-parser^0.16.00.17.0out of date
 zenoh-buffers=1.5.01.5.0up to date
 zenoh-codec=1.5.01.5.0up to date
 zenoh-config=1.5.01.5.0up to date
 zenoh-core=1.5.01.5.0up to date
 zenoh-protocol=1.5.01.5.0up to date
 zenoh-result=1.5.01.5.0up to date
 zenoh-runtime=1.5.01.5.0up to date
 zenoh-util=1.5.01.5.0up 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.