CVE-2023-41880 Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64
Wasmtime miscompiles specific SIMD instructions on x86_64, causing incorrect results in WebAssembly programs without breaking sandbox isolation.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-41880?
CVE-2023-41880 is a low-severity vulnerability in bytecodealliance wasmtime, published on 15 Sep 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Wasmtime is a standalone runtime for WebAssembly. Wasmtime versions from 10.0.0 to versions 10.02, 11.0.2, and 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.
Wasmtime versions 10.0.2, 11.0.2, and 12.0.2 are all patched to no longer have this miscompilation. 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.
Weakness: CWE-193
Which versions are affected by CVE-2023-41880?
7 open source packages ship an affected version, including wasmtime. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
wasmtime crates.io | From 0.0.0-0 | 10.0.2, 11.0.2, 12.0.2 |
wasmtime crates.io | From 10.0.0 | 10.0.2 |
wasmtime crates.io | From 10.0.0 | 10.0.2 |
wasmtime crates.io | From 11.0.0 | 11.0.2 |
wasmtime crates.io | From 11.0.0 | 11.0.2 |
wasmtime crates.io | From 12.0.0 | 12.0.2 |
1 more packages
wasmtime crates.io | From 12.0.0 | 12.0.2 |
Products include Bytecodealliance Wasmtime.
How do I fix CVE-2023-41880?
Upgrade wasmtime to a fixed version for your release line: 10.0.2, 11.0.2 or 12.0.2.
Is CVE-2023-41880 being exploited?
There is no known exploitation of CVE-2023-41880 in the wild and no public exploit code.
Other vulnerabilities in bytecodealliance wasmtime
- CVE-2026-34971 Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift
- CVE-2026-34987 Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
- CVE-2022-39393 Wasmtime vulnerable to data leakage between instances in the pooling allocator
- CVE-2022-24791 Use after free in Wasmtime
- CVE-2026-47261 Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction
Sources
Also known as DEBIAN-CVE-2023-41880, GHSA-gw5p-q8mj-p7gh, RUSTSEC-2023-0091.