CVE-2022-39394: wasmtime_trap_code C API function has out of bounds write vulnerability
(updated )
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.
References
- github.com/advisories/GHSA-h84q-m8rr-3v9q
- github.com/bytecodealliance/wasmtime
- 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
- rustsec.org/advisories/RUSTSEC-2022-0097.html
Code Behaviors & Features
Detect and mitigate CVE-2022-39394 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →