3 ms·

Any time these come up i don't find a comprehensive analysis on security. The best, supposedly most secure libraries in the world get significant vulnerabilitie

• tpetry 6y ago
  This is not make any software magically secure. It‘s only purpose is to _sandbox_ a library to prevent it doing anything malicious. As wasm cant do any more than computing you simply contain the library, it cant anymore open any files, make network calls, etc.
  • mehrdadn 6y ago
    > As wasm cant do any more than computing you simply contain the library, it cant anymore open any files, make network calls, etc. I wish the world was that simple.
  • wahern 6y ago
    > As wasm cant do any more than computing you simply contain the library, it cant anymore open any files, make network calls, etc. That presumes the WASM implementation is bug free, which is not a great presumption, especially for the more sophisticated implementations with JIT engines, and even more so for those adding multi-threading, GC, etc.
  • pjmlp 6y ago
    It doesn't prevent Heartbleed like kind of attacks. Also doesn't prevent internal memory corruption attacks that expose unintended behaviors from the public module interface.
• kevingadd 6y ago
  See this paper for some recent research on the subject: http://www.software-lab.org/publications/usenixSec2020-WebAssembly.pdf http://www.software-lab.org/publications/usenixSec2020-WebAs... You can probably use wasm to build a very comprehensive secure sandbox but right now it's actually somewhat of a regression when you care about making an application secure. Your OS is safe, at least, as long as you don't let the app make any syscalls.