Two-Faces of WASM Security
summary
Shows concrete exploits against WASM modules compiled with Emscripten toolchain: buffer overflows and format-string-style overwrites of linear memory that replace function-table entries to call arbitrary built-ins and exfiltrate document.cookie, and a type-confusion trick that bypasses WASM signature checks. Demonstrates real-world misuse — CryptoNight miners embedded in pages and extensions, stable module hashes enabling detection, and recommends mitigations like control-flow integrity/CFI and thorough C/C++ sanitization from the supplied GitHub examples.
AI-written summary · about
chapters (10)
- 0:00Introduction to WASM security
- 2:51Why use WebAssembly
- 5:02WASM basics and example
- 7:13WASM security design
- 8:20Malicious WASM modules
- 10:29Cryptojacking with WASM
- 12:56C/C++ bugs in WASM
- 17:07Type confusion in WASM
- 18:12Summary and future work
- 18:57Q&A session
related talks
43mWebAssembly Is All You Need:Exploiting Chrome and the V8 Sandbox 10+ times with WASM
48mDon't Trust Anything! Real-world Uses For WebAssembly
24mBitcoin Web Application Security
24mWriting Secure JavaScript
24mWasm't That Easy: Securing MCP With Wasm Sandboxes
26mSyscall Me by Your Name: Sandboxing Wasm Programs
51mExploiting Hardware Glitches And Side Channels In Perfect Software
23mJavaScript attack surface