wasmtime_jit_debug Dumps Undefined Memory by `JitDumpFile`
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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](https://github.com/bytecodealliance/wasmtime/pull/10963). Please open an issue in Wasmtime if you're using this crate directly.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | wasmtime-jit-debug (crates.io) | before 24.0.0 | 24.0.0 | Patch available | GHSA-9ghp-w2hm-vfpf |
- wasmtime-jit-debug (crates.io) Vendor— Affected before 24.0.0 Fixed in 24.0.0 Patch available GHSA-9ghp-w2hm-vfpf
Remediation
- Fix · GHSA-9ghp-w2hm-vfpf wasmtime-jit-debug (crates.io) Fixed in 24.0.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9ghp-w2hm-vfpf
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences