Bytecodealliance wasm-micro-runtime
WebAssembly Micro Runtime: Heap Buffer Overflow in WAMR WASI poll_oneoff Output Buffer
WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. Prior to 2.4.5, wasi_poll_oneoff in core/iwasm/libraries/libc-wasi/libc_wasi_wrapper.c validates the output pointer for only one wasi_event_t, while wasmtime_ssp_poll_oneoff in core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c can write as many events as the guest-controlled nsubscriptions value. A crafted guest module can provide multiple subscriptions that produce events while positioning an output region large enough for only one event, causing a later out[nevents] write to cross the validated Wasm linear-memory boundary into adjacent host heap memory. The overwrite contains partly attacker-controlled event data and can reliably crash the host process, with further confidentiality or integrity consequences depending on heap layout. This issue is fixed in version 2.4.5.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.4.5
Fixed in 2.4.5
Mitigation
Upgrade wasm-micro-runtime to 2.4.5 or later.
References
- Vendor advisory github.com/wasm-micro-runtime/wasm-micro-runti…
- Patch github.com/wasm-micro-runtime/wasm-micro-runti…
- Patch github.com/wasm-micro-runtime/wasm-micro-runti…
1 more
- Release notes github.com/wasm-micro-runtime/wasm-micro-runti…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.