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

(15 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.93up to date
 async-trait^0.1.710.1.83up to date
 bytes^1.41.8.0up to date
 futures^0.3.270.3.31up to date
 http^1.0.01.1.0up to date
 http-body^1.0.01.0.1up to date
 http-body-util^0.1.00.1.2up to date
 hyper^1.0.11.5.0up to date
 rustls ⚠️^0.21.60.23.16out of date
 tokio^1.26.01.41.1up to date
 tokio-rustls^0.24.00.26.0out of date
 tracing^0.1.260.1.40up to date
 wasmtime^18.0.426.0.1out of date
 wasmtime-wasi^18.0.426.0.1out of date
 webpki-roots^0.25.20.26.6out of date

Dev dependencies

(7 total, 2 outdated)

CrateRequiredLatestStatus
 base64^0.21.00.22.1out of date
 futures^0.3.270.3.31up to date
 sha2^0.10.20.10.8up to date
 test-log^0.20.2.16up to date
 tokio^1.26.01.41.1up to date
 tracing-subscriber^0.3.10.3.18up to date
 wasmtime^18.0.426.0.1out of date

Security Vulnerabilities

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.