Wasmtime panics when transcoding misaligned utf-16 strings
- 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 24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.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: partial
Summary
Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime's implementation of transcoding strings into the Component Model's utf16 or latin1+utf16 encodings improperly verified the alignment of reallocated strings. This meant that unaligned pointers could be passed to the host for transcoding which would trigger a host panic. This panic is possible to trigger from malicious guests which transfer very specific strings across components with specific addresses. Host panics are considered a DoS vector in Wasmtime as the panic conditions are controlled by the guest in this situation. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bytecodealliance wasmtime
fixed in 24.0.7; From 25.0.0 · fixed in 36.0.7; From 37.0.0 · fixed in 42.0.2; From 43.0.0 · fixed in 44.0.1
- wasmtimecrates.io
fixed in 24.0.7
- wasmtimecrates.io
From 25.0.0 · fixed in 36.0.7
- wasmtimecrates.io
From 37.0.0 · fixed in 42.0.2
- wasmtimecrates.io
From 43.0.0 · fixed in 43.0.1
- wasmtimecrates.io
From 0.0.0-0 · fixed in 24.0.7; From 25.0.0 · fixed in 36.0.7; From 37.0.0 · fixed in 42.0.2; From 43.0.0 · fixed in 43.0.1