wasmtime-jit-debug
Affected
- introduced
0, fixed24.0.0(semver)
Fixed versions
24.0.0
Fix
- Fixed version
24.0.0cargo update -p wasmtime-jit-debug --precise 24.0.0
Advisory
Also known as: RUSTSEC-2024-0442
wasmtime_jit_debug Dumps Undefined Memory by JitDumpFile
The unsound function dump_code_load_record uses from_raw_parts to directly convert the pointer addr and len into a slice without any validation and that memory block would be dumped.
Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires the caller to guarantee that the addr is valid and len must not overflow. Otherwise, the function could dump the memory into file illegally, causing memory leak.
> Note: this is an internal-only crate in the Wasmtime project not intended for external use and is more strongly signaled nowadays as of bytecodealliance/wasmtime#10963. Please open an issue in Wasmtime if you're using this crate directly.
Medium Basis: The source's own band: MODERATE
0, fixed 24.0.0 (semver)24.0.0
24.0.0cargo update -p wasmtime-jit-debug --precise 24.0.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0