There is a bug in Wasmtime’s C API implementation where the definition of the wasmtime_trap_code
does not match its declared signature in the wasmtime/trap.h
header file. This discrepancy causes the function implementation to perform a 4-byte write into a 1-byte buffer provided by the caller. This can lead to three zero bytes being written beyond the 1-byte location provided by the caller.
This bug has been patched and users should upgrade to Wasmtime 2.0.2.
This can be worked around by providing a 4-byte buffer casted to a 1-byte buffer when calling wasmtime_trap_code
. Users of the wasmtime
crate are not affected by this issue, only users of the C API function wasmtime_trap_code
are affected.
If you have any questions or comments about this advisory:
github.com/advisories/GHSA-h84q-m8rr-3v9q
github.com/bytecodealliance/wasmtime/commit/087d9d7becf7422b3f872a3bcd5d97bb7ce7ff36
github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493
github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q
groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA
nvd.nist.gov/vuln/detail/CVE-2022-39394