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 dumpcodeload_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.
{ "nvd_published_at": null, "cwe_ids": [ "CWE-119" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-06-17T15:37:56Z" }