CVE & CISA-KEV Catalog

CVE-2021-39219

MEDIUM
6.3
CVSS v3
NVD

Description

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`.

How to fix

Remediation Available
wasmtimeNVD
Affected:< 0.30.0Fixed in:0.30.0CVE-2021-39219derived from NVD

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityHigh
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Exploit Intelligence

0.29%probability of exploitation in 30 days
21stpercentile

Low risk: more likely to be exploited than 21% of all known CVEs.

References

Third-Party Advisory1
Product1

Related Vulnerabilities

Other CWE-843 (Type Confusion) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2011-0611High8.899%KEVFix
CVE-2012-0507Critical9.898%KEV + Ransom-
CVE-2017-8291High7.897%KEVFix
CVE-2019-0752High7.582%KEV + Ransom-
CVE-2017-0037High8.180%KEV-
CVE-2016-7201High8.880%KEV-
Embed a live status badge for CVE-2021-39219
CVE-2021-39219 severity badge

Markdown

[![CVE-2021-39219](https://tridentstack.com/cve/badge/CVE-2021-39219.svg)](https://tridentstack.com/cve/CVE-2021-39219)

HTML

<a href="https://tridentstack.com/cve/CVE-2021-39219"><img src="https://tridentstack.com/cve/badge/CVE-2021-39219.svg" alt="CVE-2021-39219"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Start free

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.