3 ms·
Yes but the impact of a wasm buffer overflow is completely different to a C buffer overflow. A C buffer overflow can (sometimes) let you execute arbitrary code.
by IshKebab 5y ago
Yes but the impact of a wasm buffer overflow is completely different to a C buffer overflow. A C buffer overflow can (sometimes) let you execute arbitrary code. A wasm one will just result in data corruption.
That data corruption may be exploitable (e.g. if it lets you overwrite a password) but those kinds of attacks are much much rarer than the kind that wasm prevents.
- pjmlp 5y agoBeing rarer doesn't make them nonexistent, as the WebAssembly advocacy tends to be around most places.
- IshKebab 5y agoThis blog post explicitly calls out that out: > the programmer only needs to sanitize any values that come from the sandbox (since they could be maliciously-crafted), a task which RLBox makes easy with a tainting layer. I don't think I've ever heard any WebAssembly advocates saying that it magically solves all security issues.