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.
deno_tls(10 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| deno_core | ^0.324.0 | 0.326.0 | out of date |
| deno_native_certs | ^0.3.0 | 0.3.1 | up to date |
| rustls ⚠️ | ^0.23.11 | 0.23.20 | maybe insecure |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| rustls-tokio-stream | =0.3.0 | 0.3.0 | up to date |
| rustls-webpki | ^0.102 | 0.102.8 | up to date |
| serde | ^1.0.149 | 1.0.216 | up to date |
| thiserror | ^2.0.3 | 2.0.7 | up to date |
| tokio | ^1.36.0 | 1.42.0 | up to date |
| webpki-roots | ^0.26 | 0.26.7 | up to date |
rustls: rustls network-reachable panic in `Acceptor::accept`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.