CVE-2024-47763
Wasmtime runtime crash when combining tail calls with trapping imports
Reported by github_m · Published October 9, 2024
wasmtime is fixed in 25.0.2, 24.0.1, 23.0.3 and 2 more (crates.io)
Wasmtime is an open source runtime for WebAssembly. Wasmtime's implementation of WebAssembly tail calls combined with stack traces can result in a runtime crash in certain WebAssembly modules. The runtime crash may be undefined behavior if Wasmtime was compiled with Rust 1.80 or prior. The runtime crash is a deterministic process abort when Wasmtime is compiled with Rust 1.81 and later. WebAssembly tail calls are a proposal which relatively recently reached stage 4 in the standardization process. Wasmtime first enabled support for tail calls by default in Wasmtime 21.0.0, although that release contained a bug where it was only on-by-default for some configurations. In Wasmtime 22.0.0 tail calls were enabled by default for all configurations. The specific crash happens when an exported function in a WebAssembly module (or component) performs a `return_call` (or `return_call_indirect` or `return_call_ref`) to an imported host function which captures a stack trace (for example, the host function raises a trap). In this situation, the stack-walking code previously assumed there was always at least one WebAssembly frame on the stack but with tail calls that is no longer true. With the tail-call proposal it's possible to have an entry trampoline appear as if it directly called the exit trampoline. This situation triggers an internal assert in the stack-walking code which raises a Rust `panic!()`. When Wasmtime is compiled with Rust versions 1.80 and prior this means that an `extern "C"` function in Rust is raising a `panic!()`. This is technically undefined behavior and typically manifests as a process abort when the unwinder fails to unwind Cranelift-generated frames. When Wasmtime is compiled with Rust versions 1.81 and later this panic becomes a deterministic process abort. Overall the impact of this issue is that this is a denial-of-service vector where a malicious WebAssembly module or component can cause the host to crash. There is no other impact at this time other than availability of a service as the result of the crash is always a crash and no more. This issue was discovered by routine fuzzing performed by the Wasmtime project via Google's OSS-Fuzz infrastructure. We have no evidence that it has ever been exploited by an attacker in the wild. All versions of Wasmtime which have tail calls enabled by default have been patched: * 21.0.x - patched in 21.0.2 * 22.0.x - patched in 22.0.1 * 23.0.x - patched in 23.0.3 * 24.0.x - patched in 24.0.1 * 25.0.x - patched in 25.0.2. Wasmtime versions from 12.0.x (the first release with experimental tail call support) to 20.0.x (the last release with tail-calls off-by-default) have support for tail calls but the support is disabled by default. These versions are not affected in their default configurations, but users who explicitly enabled tail call support will need to either disable tail call support or upgrade to a patched version of Wasmtime. The main workaround for this issue is to disable tail support for tail calls in Wasmtime, for example with `Config::wasm_tail_call(false)`. Users are otherwise encouraged to upgrade to patched versions.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| wasmtime | crates.io | 25.0.2, 24.0.1, 23.0.3, 22.0.1, 21.0.2 |
| wasmtime-bin | PyPI | 25.0.2, 23.0.3, 22.0.1, 21.0.2, 21.0.0 |
| wizer | Chainguard | 7.0.5-r1 |
| wasmcloud | Chainguard | 1.3.0-r1 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| bytecodealliance | wasmtime | >= 21.0.0, < 21.0.2, >= 22.0.0, < 22.0.1, >= 23.0.0, < 23.0.3 |
| chainguard | wizer | 0 |
| chainguard | wasmcloud | 0 |
| PyPI | wasmtime-bin | 21.0.0, 25.0.0, 23.0.0 |
| crates.io | wasmtime | 24.0.0, 12.0.0, 22.0.0 |
| wolfi | wash | 0 |
| wolfi | wizer | 0 |
| chainguard | zed | 0 |
| bytecodealliance | wasmtime | 23.0.0, 25.0.0, 24.0.0 |
| wolfi | zed | 0 |
| wolfi | wasmcloud | 0 |
| chainguard | wash | 0 |
Timeline
- Oct 2, 2024 CVE Published
- Oct 9, 2024 CVE Updated
- Oct 9, 2024 PoC Published
- Oct 10, 2024 EPSS Score (30 in total, the first dated here)
- Oct 14, 2024 Coalition ESS Score (13 in total, the first dated here)
- Jan 3, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-47763
vulnetix vdb fixes CVE-2024-47763
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-47763/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q8hx-mm92-4wvg x_refsource_CONFIRM
- https://github.com/bytecodealliance/wasmtime/pull/8540 x_refsource_MISC
- https://github.com/bytecodealliance/wasmtime/pull/8682 x_refsource_MISC
- https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_tail_call x_refsource_MISC
- https://github.com/WebAssembly/proposals x_refsource_MISC
- https://github.com/webassembly/tail-call x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2024-47763 advisory
- https://github.com/advisories/GHSA-q8hx-mm92-4wvg advisory
- https://github.com/bytecodealliance/wasmtime/pull/6774 patch
- https://github.com/bytecodealliance/wasmtime/commit/0ebe54d05f0e1f6c64b7c8bb48c9e9f6c95cacba patch
- https://rustsec.org/advisories/RUSTSEC-2024-0440.html url
- https://github.com/pypa/advisory-database/tree/main/vulns/wasmtime-bin/PYSEC-2024-312.yaml advisory
- https://github.com/bytecodealliance/wasmtime url