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 wasmtime-wasi-http

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.890.1.92up to date
 bytes^1.11.11.12.1up to date
 futures^0.3.310.3.34up to date
 http^1.3.11.5.0up to date
 http-body^1.0.11.1.0up to date
 http-body-util^0.1.30.1.5up to date
 hyper^1.9.01.11.1up to date
 pin-project-lite^0.2.140.2.17up to date
 rustls ⚠️^0.230.23.44maybe insecure
 tokio^1.51.11.53.1up to date
 tokio-rustls^0.26.40.26.5up to date
 tokio-util^0.7.160.7.19up to date
 tracing^0.1.410.1.44up to date
 wasmtime^48.0.248.0.2up to date
 wasmtime-wasi^48.0.248.0.2up to date
 wasmtime-wasi-io^48.0.248.0.2up to date
 webpki-roots^1.0.71.0.9up to date

Dev dependencies

(11 total, 3 outdated)

CrateRequiredLatestStatus
 base64^0.22.10.23.1out of date
 env_logger^0.11.50.11.11up to date
 flate2^1.1.41.1.10up to date
 futures^0.3.310.3.34up to date
 sha2^0.10.20.11.0out of date
 tempfile^3.27.03.27.0up to date
 test-log^0.2.180.2.21up to date
 tokio^1.51.11.53.1up to date
 tracing-subscriber^0.3.200.3.23up to date
 wasm-compose^0.254.00.259.0out of date
 wasmtime^48.0.248.0.2up 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.