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

(70 total, 29 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.100up to date
 async-trait^0.10.1.89up to date
 base64^0.210.22.1out of date
 bincode^1.33.0.0out of date
 blake3^1.01.8.2up to date
 bytecheck^0.6.80.8.2out of date
 bytes^11.11.0up to date
 cfg-if^1.01.0.4up to date
 chrono^0.4.310.4.42up 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.3.4out of date
 heapless^0.7.160.9.2out of date
 hex^0.40.4.3up to date
 http^0.2.81.4.0out of date
 hyper ⚠️^0.141.8.1out of date
 js-sys^0.3.640.3.83up to date
 lazy_static^1.41.5.0up to date
 libc^0.20.2.178up to date
 linked_hash_set^0.10.1.6up to date
 lz4_flex^0.110.12.0out of date
 num_enum^0.5.70.7.5out of date
 once_cell^1.17.01.21.3up to date
 petgraph^0.6.30.8.3out of date
 pin-project^1.0.121.1.10up to date
 rand^0.80.9.2out of date
 rayon^1.7.01.11.0up to date
 reqwest^0.110.12.28out of date
 rkyv^0.7.400.8.12out of date
 rusty_pool^0.7.00.7.0up to date
 semver^1.0.171.0.27up to date
 serde^1.01.0.228up to date
 serde_cbor^0.11.20.11.2up to date
 serde_derive^11.0.228up to date
 serde_json^11.0.148up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 sha2^0.100.10.9up to date
 shared-buffer^0.1.40.1.4up to date
 tempfile^3.6.03.24.0up to date
 term_size^0.30.3.2up to date
 termios^0.30.3.3up to date
 thiserror^12.0.17out of date
 tokio ⚠️^11.48.0maybe insecure
 tokio-stream^0.10.1.17up to date
 tower^0.4.130.5.2out of date
 tower-http^0.4.00.6.8out of date
 tracing^0.1.370.1.44up to date
 typetag^0.10.2.21out of date
 url^2.3.12.5.7up to date
 urlencoding^22.1.3up to date
 virtual-fs^0.11.20.601.0out of date
 virtual-mio^0.3.10.601.0out of date
 virtual-net^0.6.30.601.0out of date
 waker-fn^1.11.2.0up to date
 wasm-bindgen^0.2.870.2.106up to date
 wasm-bindgen-futures^0.4.370.4.56up to date
 wasmer=4.2.86.1.0out of date
 wasmer-emscripten=4.2.84.4.0out of date
 wasmer-journal^0.1.00.601.0out of date
 wasmer-types=4.2.86.1.0out of date
 wasmer-wasix-types^0.18.30.601.0out of date
 wcgi^0.1.20.3.0out of date
 wcgi-host^0.1.20.3.0out of date
 web-sys^0.3.640.3.83up to date
 webc^5.8.010.0.1out of date
 weezl^0.10.1.12up to date
 winapi^0.30.3.9up to date
 xxhash-rust^0.8.80.8.15up to date

Dev dependencies

(7 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 pretty_assertions^1.3.01.4.1up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 tracing-test^0.2.40.2.5up to date
 tracing-wasm^0.20.2.1up to date
 wasm-bindgen-test^0.3.00.3.56up to date
 wasmer=4.2.86.1.0out of date

Security Vulnerabilities

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

RUSTSEC-2021-0078

hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.

To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.

hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

RUSTSEC-2021-0079

When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.

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);

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.