> So it is cool if you allow an attacker to change the program inside? The abstract machine behind WASM is a Harvard architecture, so self-modifying code (even

> So it is cool if you allow an attacker to change the program inside? The abstract machine behind WASM is a Harvard architecture, so self-modifying code (even accidentally through attacks) is not possible. Memory safety is still a problem for languages that aren't memory safe, but since the program memory is not writeable from the program itself you can't take over control through memory safety bugs. Now whether the program interprets its data in a way that can be made exploitable is a different bug, but one that exists outside what WASM (or any virtual machine) can fix - it does mitigate the consequences however, since every module is isolated and the runtime uses capability-based security to prevent the code from accessing any system resources that it doesn't need.