Wasmtime is a standalone runtime for WebAssembly. Prior to version 2.0.2, 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 bug 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.
References
Link | Resource |
---|---|
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q | Third Party Advisory |
https://github.com/bytecodealliance/wasmtime/commit/087d9d7becf7422b3f872a3bcd5d97bb7ce7ff36 | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2022-11-10 12:15
Updated : 2022-11-16 05:31
NVD link : CVE-2022-39394
Mitre link : CVE-2022-39394
JSON object : View
CWE
CWE-787
Out-of-bounds Write
Products Affected
bytecodealliance
- wasmtime