SB20241009104 - Multiple vulnerabilities in Wasmtime
Published: October 9, 2024 Updated: April 23, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 2 vulnerabilities.
1) Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-ID: CVE-2024-47813)
CWE-ID: CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
CVSSv4: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:U/U:Clear
The vulnerability allows a local privileged user to violate WebAssembly control-flow integrity and type safety, or cause a denial of service.
The vulnerability exists due to a time-of-check time-of-use race condition in Wasmtime's internal type registry when creating and dropping multiple type instances concurrently across multiple threads associated with the same wasmtime::Engine. A local privileged user can trigger concurrent type registration and unregistration operations to violate WebAssembly control-flow integrity and type safety, or cause a denial of service.
Wasm guests cannot trigger this bug. User interaction is required.
2) Always-Incorrect Control Flow Implementation (CVE-ID: CVE-2024-47763)
CWE-ID: CWE-670 - Always-Incorrect Control Flow Implementation
CVSSv4: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/U:Clear
The vulnerability allows a local user to cause a denial of service.
The vulnerability exists due to improper handling of stack frames in stack-walking code when processing a WebAssembly module that combines tail calls with stack trace capture. A local user can execute a crafted WebAssembly module or component to cause a denial of service.
The issue is triggered when an exported function performs a return_call, return_call_indirect, or return_call_ref to an imported host function that captures a stack trace, such as by raising a trap.
Remediation
Install update from vendor's website.