RUSTSEC-2024-0442

Source
https://rustsec.org/advisories/RUSTSEC-2024-0442
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2024-0442.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2024-0442
Aliases
Published
2024-07-06T12:00:00Z
Modified
2025-10-28T06:29:24Z
Summary
Dump Undefined Memory by `JitDumpFile`
Details

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.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / wasmtime-jit-debug

Package

Name
wasmtime-jit-debug
View open source insights on deps.dev
Purl
pkg:cargo/wasmtime-jit-debug

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
24.0.0

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "arch": [],
        "functions": [
            "wasmtime_jit_debug::perf_jitdump::JitDumpFile::dump_code_load_record"
        ],
        "os": []
    }
}

Database specific

categories
[
    "memory-exposure"
]
cvss
null
informational
"unsound"
source
"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2024-0442.json"