Ecosyste.ms: Advisories

Security Advisories: GSA_kwCzR0hTQS00ODczLTM2aDktd3Y0Oc0V3A

Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime

Impact

There was an invalid free and out-of-bounds read and write bug when running Wasm that uses externrefs in Wasmtime.

To trigger this bug, Wasmtime needs to be running Wasm that uses externrefs, the host creates non-null externrefs, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where

• there are no live references at this safepoint, and
• there is a safepoint with live references earlier in this frame's function.

Under this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as externrefs that needed to be rooted for GC. At the next GC, it would be determined that nothing was referencing these bogus externrefs (because nothing could ever reference them, because they are not really externrefs) and then Wasmtime would deallocate them and run <ExternRef as Drop>::drop on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes.

Even though support for externrefs (via the reference types proposal) is enabled by default, unless you are creating non-null externrefs in your host code or explicitly triggering GCs, you cannot be affected by this bug.

We have reason to believe that the effective impact of this bug is relatively small because usage of externref is currently quite rare.

Patches

This bug has been patched and users should upgrade to Wasmtime version 0.30.0.

Additionally, we have updated our primary externref fuzz target such that it better exercises these code paths and we can have greater confidence in their correctness going forward.

Workarounds

If you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing false to wasmtime::Config::wasm_reference_types

References

• The Wasm reference types proposal, which introduces externref

For more information

If you have any questions or comments about this advisory:

• Reach out to us on the Bytecode Alliance Zulip chat
• Open an issue in the bytecodealliance/wasmtime repository

Permalink: https://github.com/advisories/GHSA-4873-36h9-wv49
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS00ODczLTM2aDktd3Y0Oc0V3A
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Moderate
Classification: General
Published: over 2 years ago
Updated: 10 months ago

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

Identifiers: GHSA-4873-36h9-wv49, CVE-2021-39218
References:

• https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4873-36h9-wv49
• https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c
• https://crates.io/crates/wasmtime
• https://nvd.nist.gov/vuln/detail/CVE-2021-39218
• https://lists.fedoraproject.org/archives/list/[email protected]/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/
• https://lists.fedoraproject.org/archives/list/[email protected]/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/
• https://rustsec.org/advisories/RUSTSEC-2021-0110.html
• https://github.com/advisories/GHSA-4873-36h9-wv49

Repository: https://github.com/bytecodealliance/wasmtime
Blast Radius: 21.4

Affected Packages