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 wasmer-wasix

Dependencies

(74 total, 19 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.110.8.11up to date
 anyhow^1.0.661.0.92up to date
 async-trait^0.10.1.83up to date
 base64^0.210.22.1out of date
 bincode^1.31.3.3up to date
 blake3^1.01.5.4up to date
 bytecheck^0.6.80.8.0out of date
 bytes^11.8.0up to date
 cfg-if^1.01.0.0up to date
 chrono^0.4.310.4.38up to date
 cooked-waker^55.0.0up to date
 dashmap^5.4.06.1.0out of date
 derivative^22.2.0up to date
 futures^0.30.3.31up to date
 getrandom^0.20.2.15up to date
 heapless^0.7.160.8.0out of date
 hex^0.40.4.3up to date
 http^1.0.01.1.0up to date
 http-body-util^0.1.10.1.2up to date
 hyper^11.5.0up to date
 hyper-util^0.1.50.1.10up to date
 js-sys^0.3.640.3.72up to date
 lazy_static^1.41.5.0up to date
 libc^0.20.2.161up to date
 linked_hash_set^0.10.1.4up to date
 lz4_flex^0.110.11.3up to date
 num_enum^0.5.70.7.3out of date
 once_cell^1.17.01.20.2up to date
 petgraph^0.6.30.6.5up to date
 pin-project^1.0.121.1.7up to date
 rand^0.80.8.5up to date
 rayon^1.7.01.10.0up to date
 reqwest^0.12.00.12.9up to date
 rkyv^0.7.400.8.8out of date
 rusty_pool^0.7.00.7.0up to date
 semver^1.0.171.0.23up to date
 serde^1.01.0.214up to date
 serde_cbor^0.11.20.11.2up to date
 serde_derive^11.0.214up to date
 serde_json^11.0.132up to date
 serde_yaml^0.9.340.9.34+deprecatedup to date
 sha2^0.100.10.8up to date
 shared-buffer^0.1.40.1.4up to date
 tempfile^3.6.03.13.0up to date
 terminal_size^0.3.00.4.0out of date
 termios^0.30.3.3up to date
 thiserror^11.0.68up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-stream^0.10.1.16up to date
 tower^0.4.130.5.1out of date
 tower-http^0.5.00.6.1out of date
 tracing^0.1.370.1.40up to date
 typetag^0.10.2.18out of date
 url^2.3.12.5.3up to date
 urlencoding^22.1.3up to date
 virtual-fs^0.15.00.19.0out of date
 virtual-mio^0.3.10.5.0out of date
 virtual-net^0.7.00.11.0out of date
 waker-fn^1.11.2.0up to date
 wasm-bindgen^0.2.870.2.95up to date
 wasm-bindgen-futures^0.4.370.4.45up to date
 wasmer=4.3.55.0.0out of date
 wasmer-config^0.5.00.10.0out of date
 wasmer-emscripten=4.3.54.4.0out of date
 wasmer-journal^0.7.00.12.0out of date
 wasmer-types=4.3.55.0.0out of date
 wasmer-wasix-types^0.25.00.30.0out of date
 wcgi^0.2.00.2.0up to date
 wcgi-host^0.2.00.2.0up to date
 web-sys^0.3.640.3.72up to date
 webc^6.0.0-rc16.1.0up to date
 weezl^0.10.1.8up to date
 winapi^0.30.3.9up to date
 xxhash-rust^0.8.80.8.12up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 pretty_assertions^1.3.01.4.1up to date
 tokio ⚠️^11.41.0maybe insecure
 tracing-subscriber^0.30.3.18up to date
 tracing-test^0.2.40.2.5up to date
 tracing-wasm^0.20.2.1up to date
 wasm-bindgen-test^0.3.00.3.45up to date
 wasmer=4.3.55.0.0out of date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);