Executive Summary

CVE-2025-15413 is a memory corruption vulnerability in Wasm3 up to version 0.5.0, affecting the functions op_SetSlot_i32 and op_CallIndirect in the file m3_exec.h. The vulnerability occurs due to insufficient bounds checking, leading to out-of-bounds memory reads and writes. Specifically, op_CallIndirect performs indirect function calls using an index into a function table without proper validation, causing segmentation faults from invalid memory access. Similarly, op_SetSlot_i32 writes 32-bit integer values into slots on the WebAssembly interpreter stack without validating slot indices or stack boundaries, resulting in out-of-bounds writes. These flaws cause crashes (segmentation faults) and memory corruption, potentially allowing arbitrary code execution. The issue requires local access to exploit and is reproducible with provided test cases. [1, 2, 3, 5]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to memory corruption in the Wasm3 interpreter, causing crashes (segmentation faults) and potentially allowing an attacker to execute arbitrary code. Since the vulnerability involves out-of-bounds reads and writes, it compromises the confidentiality, integrity, and availability of the system running Wasm3. The exploit requires local access but is easy to execute, and a public proof-of-concept exploit is available. Because the project currently has no active maintainer and no mitigations are published, affected users face a significant security risk, especially in production environments. [3, 4, 5]

Useful 0 Not Useful 0

Detection Guidance

The vulnerability can be detected by reproducing the issue using the provided test case with the command `./wasm3 repro`. Detection involves observing a segmentation fault (SEGV) caused by memory access violations in the functions op_CallIndirect or op_SetSlot_i32. The use of AddressSanitizer (ASAN) is recommended to identify the memory corruption during execution, as it reports the faulting addresses and stack traces pinpointing the vulnerability. [1, 2, 3, 5]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include restricting local access to systems running the vulnerable Wasm3 versions, as the attack requires local access. Since the project currently has no active maintainer and no known patches or countermeasures are available, users are advised to consider replacing Wasm3 with alternative products to avoid exploitation. Monitoring for exploitation attempts and limiting user privileges can also help reduce risk. [4]

Useful 0 Not Useful 0