wasmtime
Affected
- introduced
10.0.0, fixed10.0.2(semver)
Fixed versions
10.0.2
Fix
- Fixed version
10.0.2cargo update -p wasmtime --precise 10.0.2
Advisory
Also known as: CVE-2023-41880, RUSTSEC-2023-0091
Miscompilation of wasm i64x2.shr_s instruction with constant input on x86_64
Impact
Wasmtime versions from 10.0.0 to 12.0.1 contain a miscompilation of the WebAssembly i64x2.shr_s instruction on x86_64 platforms when the shift amount is a constant value that is larger than 32. Only x86_64 is affected so all other targets are not affected by this. The miscompilation results in the instruction producing an incorrect result, namely the low 32-bits of the second lane of the vector are derived from the low 32-bits of the second lane of the input vector instead of the high 32-bits. The primary impact of this issue is that any WebAssembly program using the i64x2.shr_s with a constant shift amount larger than 32 may produce an incorrect result.
This issue is not an escape from the WebAssembly sandbox. Execution of WebAssembly guest programs will still behave correctly with respect to memory sandboxing and isolation from the host. Wasmtime considers non-spec-compliant behavior as a security issue nonetheless.
This issue was discovered through fuzzing of Wasmtime's code generator Cranelift.
Patches
Wasmtime versions 10.0.2, 11.0.2, and 12.0.2 are all patched to no longer have this miscompilation.
Workarounds
This issue only affects x86_64 hosts and the only workaround is to either scan for this pattern in wasm modules which is nontrivial or to disable the SIMD proposal for WebAssembly. Users prior to 10.0.0 are unaffected by this vulnerability.
References
Low Basis: The source's own band: LOW
10.0.0, fixed 10.0.2 (semver)10.0.2
10.0.2cargo update -p wasmtime --precise 10.0.211.0.0, fixed 11.0.2 (semver)11.0.2
11.0.2cargo update -p wasmtime --precise 11.0.212.0.0, fixed 12.0.2 (semver)12.0.2
12.0.2cargo update -p wasmtime --precise 12.0.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0