News for hackers. Stuff that matters.
Re:The Bytecode Alliance: Building a secure, composable futu... by pjmlp on Tuesday November 12, 2019 @01:45PM (#21516805)
What about fixing the lack of bounds checking when multiple data elements are mapped into the same linear memory block?

This leaves the door open for trying to influence behaviour of C and C++ generated WebAssembly modules, by corrupting their internal state via invalid data.

Re:The Bytecode Alliance: Building a secure, composable futu... by saagarjha on Tuesday November 12, 2019 @06:03PM (#21519215)
If you give a sandbox a capability and then there’s a bug in it, there’s always a chance that it will maliciously access those privileged resources. The only way I can see of protecting against logic bugs like these is better tooling.
Re:The Bytecode Alliance: Building a secure, composable futu... by pjmlp on Tuesday November 12, 2019 @11:41PM (#21521228)
Yeah, but then one should acknowledge those issues, and not advocate WebAssembly as if there weren't hundreds of other attempts since the late 50's.
Re:The Bytecode Alliance: Building a secure, composable futu... by saagarjha on Wednesday November 13, 2019 @04:53AM (#21522496)
They don't mention them because their focus is on other aspects of safety.
Re:The Bytecode Alliance: Building a secure, composable futu... by pjmlp on Wednesday November 13, 2019 @06:55AM (#21523096)
Either one is actually serious about security across the whole stack, or not.