Compromising the Security of WASM

In this video we show three different methods for hacking and breaking the security of wasm programs.
We contrast/compare with Linux and the Nanos Unikernel and explain why these security controls are necessary and beneficial.
While unikernels and wasm are not mutually exclusive (you can run wasm runtimes inside of a unikernel) we caution the viewer about the security risks.

[@offlinemark]

awesome, love this technical content 👌

[@almc8445]

Isn’t the whole idea of WASM that it’s for client side code? In which case you should be assuming that “Read-Only” isn’t a thing that exists anyway. You always assume the client is compromised.
This is an application design issue, if you need a value stored or calculated securely, it should be happening server-side anyway?

[@nanovms7360]

No. Quite a few companies/organizations are explicitly building for wasm on the server-side, in particular in the 'function-as-a-service' space there is quite a lot of attention to using wasm in this manner.