2 ms·
That's pretty limited way to look at it. You don't need to escape the sandbox to do harm. You can have your app in perfect sandbox where nothing can escape the
by ilyt 4y ago
That's pretty limited way to look at it. You don't need to escape the sandbox to do harm.
You can have your app in perfect sandbox where nothing can escape then have a memory safety bug inside allowing user to get to the stuff of another user (because your sandboxed app talking with sandboxed database still have one set of credentials to do everything)
There is of course https://xkcd.com/1200/ https://xkcd.com/1200/ for that.
And no "move that separation to DB" also isn't a solution.
- flohofwoe 4y agoI agree, same with popular multiplayer games for instance which could be exploited by memory safety bugs in the network protocol implementation. But these are cases where just implementing a couple of critical modules either with a memory-safe language, or using code generation (or both) to reduce the amount of 'manual bugs' go a long way. AFAIK exploits almost always happen in places where data comes into the system, so those are the places to focus on.