4 ms·
I'd be interested in hearing more about this if you can point to some resources.
by anderspitman 5y ago
I'd be interested in hearing more about this if you can point to some resources.
- pjmlp 5y agoYou can start here, "USENIX Security '20 - Everything Old is New Again: Binary Security of WebAssembly" https://www.youtube.com/watch?v=glL__xjviro https://www.youtube.com/watch?v=glL__xjviro Then there are the issues that since WebAssembly doesn't prevent memory corruption, while RCE attacks or sandboxing breaks are not possible, by producing memory corruption, it is possible to eventually trigger alternative code paths that wouldn't be possible in normal circumstances. A contrived use case would be to validate a user with higher credentials that they are supposed to have, in a WASM based security module. Then since the external calls from the module are configured from the runtime, one can do man on the middle attacks on the functions being called from the module, thus access data that it wasn't supposed to be made available in normal cases. And I bet that when the hacker community starts having fun with WebAssembly, as much as they have had with other bytecode formats, more issues will be found.
- anderspitman 5y agoThanks!