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.
wasi-experimental-http-wasmtime(12 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.82 | up to date |
| bytes | ^1 | 1.6.0 | up to date |
| futures | ^0.3 | 0.3.30 | up to date |
| http | ^0.2 | 1.1.0 | out of date |
| reqwest | ^0.11 | 0.12.4 | out of date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| tokio ⚠️ | ^1.4.0 | 1.37.0 | maybe insecure |
| tracing | ^0.1 | 0.1.40 | up to date |
| url | ^2.2.1 | 2.5.0 | up to date |
| wasi-common | ^0.30 | 20.0.0 | out of date |
| wasmtime ⚠️ | ^0.30 | 20.0.0 | out of date |
| wasmtime-wasi | ^0.30 | 20.0.0 | out of date |
wasmtime: Bug in pooling instance allocatorbug in Wasmtime's implementation of its pooling instance allocator where when a linear memory is reused for another instance the initial heap snapshot of the prior instance can be visible, erroneously to the next instance.
Mitigations are described here.
wasmtime: Bug in Wasmtime implementation of pooling instance allocatorBug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory.
In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator.
This bug is not applicable with the default settings of the wasmtime crate.
This bug can only be triggered by setting InstanceLimits::memory_pages to zero.
This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory.
All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);