Out-of-bounds write via C API signature mismatch
Published Nov 10, 2022 · Updated Apr 23, 2025
Out-of-bounds write in Wasmtime before 2.0.2 allows attackers to corrupt adjacent memory via the C API wasmtime_trap_code function. Its implementation writes four bytes although the header declares a one-byte output buffer, placing three zero bytes beyond the caller's allocation. Exploitation requires code that invokes this C API with the undersized buffer; the Rust wasmtime crate API is unaffected, while memory corruption can crash or destabilize the embedding process.
Summary
What happened
Out-of-bounds write in Wasmtime before 2.0.2 allows attackers to corrupt adjacent memory via the C API wasmtime_trap_code function. Its implementation writes four bytes although the header declares a one-byte output buffer, placing three zero bytes beyond the caller's allocation. Exploitation requires code that invokes this C API with the undersized buffer; the Rust wasmtime crate API is unaffected, while memory corruption can crash or destabilize the embedding process.
The record
- CVE
- CVE-2022-39394
- Published
- Nov 10, 2022
- Updated
- Apr 23, 2025
- Vendor
- Bytecode Alliance
- Product
- Wasmtime
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 10, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo