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 megalodon

Dependencies

(23 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.800.1.89up to date
 chrono^0.4.380.4.44up to date
 futures-util^0.3.300.3.32up to date
 hex^0.40.4.3up to date
 mime_guess^2.02.0.5up to date
 oauth2^5.05.0.0up to date
 rand^0.80.10.0out of date
 regex^1.10.41.12.3up to date
 reqwest^0.12.30.13.2out of date
 rustls ⚠️^0.230.23.37maybe insecure
 rustls-native-certs^0.80.8.3up to date
 rustls-pki-types^11.14.0up to date
 serde^1.0.1971.0.228up to date
 serde_json^1.0.1151.0.149up to date
 sha1^0.100.10.6up to date
 thiserror^2.0.122.0.18up to date
 tokio^1.37.01.49.0up to date
 tokio-tungstenite^0.270.28.0out of date
 tokio-util^0.7.100.7.18up to date
 tracing^0.1.400.1.44up to date
 url^2.5.02.5.8up to date
 urlencoding^2.12.1.3up to date
 uuid^1.81.21.0up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tracing-subscriber^0.3.200.3.22up 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.