News for hackers. Stuff that matters.

A comment on WebAssembly doesn’t make unsafe languages safe. Parent comment

Re:WebAssembly doesn’t make unsafe languages safe by hackcasual on Sunday November 25, 2018 @07:35PM (#18530061)
It does in the sense that it totally protects the stack and doesn't allow creating new executable memory. Control flow can be manipulated, but then only via changing function pointers to other functions of the same type
[ Parent | on HN ]
Re:WebAssembly doesn’t make unsafe languages safe by pjmlp on Monday November 26, 2018 @12:12AM (#18531223)
Control flow can also be manipulated via memory corruption, making the existing code take other decisions, due to non valid semantic states.
[ Parent | on HN ]
Re:WebAssembly doesn’t make unsafe languages safe by hackcasual on Monday November 26, 2018 @01:32AM (#18531559)
Sure, but that's even weaker, since you can't even create new control flows, just cause surprising ones.
[ Parent | on HN ]
Re:WebAssembly doesn’t make unsafe languages safe by pjmlp on Monday November 26, 2018 @03:23AM (#18531885)
It is enough to work around authentication checks, for example.
[ Parent | on HN ]