Wasmtime memory corruption in cross-Engine Store APIs
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
Wasmtime before 24.0.12, 25.0.0 before 36.0.13, 37.0.0 before 46.0.2, and 47.0.0 before 47.0.3 contains a type confusion vulnerability because several Store APIs fail to validate that objects belong to the Store's Engine. Embedders mixing objects between Engines via Instance::new, StructRefPre::new, or Tag::new can trigger trampoline signature mismatches causing out-of-bounds stack writes, GC heap corruption, or panics.
From the CVE record · VulnCheck
Several Wasmtime Store APIs do not verify that objects belong to the Store’s Engine. When an embedder mixes objects between Engines through Instance::new, StructRefPre::new, or Tag::new, trampoline signature mismatches can cause out-of-bounds stack writes, GC heap corruption, or panics. The input does not specify network access, authentication, or user-interaction requirements.
Engineers using the crates.io wasmtime package should check versions before 24.0.12, 25.0.0 through versions before 36.0.13, 37.0.0 through versions before 46.0.2, and 47.0.0 through versions before 47.0.3.