Chainbytecodealliance · wasmtimecrates.io:wasmtime
bytecodealliance wasmtime: related fixes (2021)
3 CVEs over 3 generations, 17 Sep 2021 to 17 Sep 2021.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2021-3921617 Sep 2021 First in the chain
- CVE-2021-3921817 Sep 2021 related to CVE-2021-39216
- CVE-2021-3921917 Sep 2021 related to CVE-2021-39216related to CVE-2021-39218
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2021-39216 | 17 Sep 2021 | Use after free passing `externref`s to Wasm in Wasmtime | First in chain | 9.1 |
| CVE-2021-39218 | 17 Sep 2021 | Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime | CVE-2021-39216 · related · High | 9.0 |
| CVE-2021-39219 | 17 Sep 2021 | Wrong type for `Linker`-define functions when used across two `Engine`s | CVE-2021-39216 · related · High | 10.4 |