6.3
CVE-2021-39219
- EPSS 0.07%
- Published 17.09.2021 20:15:07
- Last modified 21.11.2024 06:18:56
- Source security-advisories@github.com
- CVE-Watchlists
- Open
Wasmtime is an open source runtime for WebAssembly & WASI. Wasmtime before version 0.30.0 is affected by a type confusion vulnerability. As a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type. Triggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`). It's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small. The fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime. This bug has been patched and users should upgrade to Wasmtime version 0.30.0. If you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`.
Data is provided by the National Vulnerability Database (NVD)
	Bytecodealliance ≫ Wasmtime  Version < 0.30.0
	Fedoraproject ≫ Fedora Version34 
	Fedoraproject ≫ Fedora Version35 
| Type | Source | Score | Percentile | 
|---|---|---|---|
| EPSS | FIRST.org | 0.07% | 0.196 | 
| Source | Base Score | Exploit Score | Impact Score | Vector string | 
|---|---|---|---|---|
| nvd@nist.gov | 6.3 | 1 | 5.2 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H  | 
| nvd@nist.gov | 3.3 | 3.4 | 4.9 | AV:L/AC:M/Au:N/C:N/I:P/A:P  | 
| security-advisories@github.com | 6.3 | 1 | 5.2 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H  | 
CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.