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.
wasmtime-wasi(23 total, 12 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.22 | 1.0.100 | up to date |
| async-trait | ^0.1.71 | 0.1.89 | up to date |
| bitflags | ^2.0 | 2.10.0 | up to date |
| bytes | ^1.4 | 1.11.0 | up to date |
| cap-fs-ext | ^3.0.0 | 4.0.0 | out of date |
| cap-net-ext | ^3.0.0 | 4.0.0 | out of date |
| cap-rand | ^3.0.0 | 4.0.0 | out of date |
| cap-std | ^3.0.0 | 4.0.0 | out of date |
| cap-time-ext | ^3.0.0 | 4.0.0 | out of date |
| fs-set-times | ^0.20.1 | 0.20.3 | up to date |
| futures | ^0.3.27 | 0.3.31 | up to date |
| io-extras | ^0.18.1 | 0.19.0 | out of date |
| io-lifetimes | ^2.0.3 | 3.0.1 | out of date |
| once_cell | ^1.12.0 | 1.21.3 | up to date |
| rustix | ^0.38.31 | 1.1.2 | out of date |
| system-interface | ^0.27.1 | 0.27.3 | up to date |
| thiserror | ^1.0.43 | 2.0.17 | out of date |
| tokio | ^1.26.0 | 1.48.0 | up to date |
| tracing | ^0.1.26 | 0.1.43 | up to date |
| url | ^2.3.1 | 2.5.7 | up to date |
| wasmtime ⚠️ | ^20.0.2 | 39.0.1 | out of date |
| wiggle | =20.0.2 | 39.0.1 | out of date |
| windows-sys | ^0.52.0 | 0.61.2 | out of date |
(5 total, 1 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempfile | ^3.1.0 | 3.23.0 | up to date |
| test-log | ^0.2 | 0.2.19 | up to date |
| tokio | ^1.26.0 | 1.48.0 | up to date |
| tracing-subscriber ⚠️ | ^0.3.1 | 0.3.22 | maybe insecure |
| wasmtime ⚠️ | ^20.0.2 | 39.0.1 | out of date |
wasmtime: Wasmtime doesn't fully sandbox all the Windows device filenamesThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c2f5-jxjv-2hh8. For more information see the GitHub-hosted security advisory.
wasmtime: Race condition could lead to WebAssembly control-flow integrity and type safety violationsThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-7qmx-3fpx-r45m. For more information see the GitHub-hosted security advisory.
wasmtime: Host panic with `fd_renumber` WASIp1 functionThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-fm79-3f68-h2fc. For more information see the GitHub-hosted security advisory.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious 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:
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.
wasmtime: Unsound API access to a WebAssembly shared linear memoryThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hc7m-r6v8-hg9q For more information see the GitHub-hosted security advisory.