Wasmi's Linear Memory has a Critical Use After Free Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.41.2, 0.47.1, 0.51.3, 1.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Wasmi is a WebAssembly interpreter focused on constrained and embedded systems. In versions 0.41.0, 0.41.1, 0.42.0 through 0.47.1, 0.50.0 through 0.51.2 and 1.0.0, Wasmi's linear memory implementation leads to a Use After Free vulnerability, triggered by a WebAssembly module under certain memory growth conditions. This issue potentially leads to memory corruption, information disclosure, or code execution. This issue is fixed in versions 0.41.2, 0.47.1, 0.51.3 and 1.0.1. To workaround this issue, consider limiting the maximum linear memory sizes where feasible.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- wasmi-labs wasmi
From 0.41.0 · fixed in 0.41.2; From 0.42.0 · fixed in 0.47.1; From 0.50.0 · fixed in 0.51.3; From 1.0.0 · fixed in 1.0.1
- wasmicrates.io
From 0.41.0 · fixed in 0.41.2
- wasmicrates.io
From 0.42.0 · fixed in 0.47.1
- wasmicrates.io
From 0.50.0 · fixed in 0.51.3
- wasmicrates.io
From 1.0.0 · fixed in 1.0.1