The actual bug is in the Turbofan JIT, not WASM. Using WASM is the method de'jour for turning arbitrary read/write/object leak into RCE. Without WASM, the writer would have to use ROP/etc, but the primitives are still there. Check out this discussion by a bunch of the big names in the field, including Niklas B who was on the team that originally found this bug: twitter.com/spoofyroot/status/137991178…

Browser gamming was killed in the name of a political agenda, meanwhile even Unity, as mentioned is not up to Flash development environment. HTML5 was the future, yet there is no way to guarantee if the customer is having either 2D or 3D acceleration working, thus the experience is random and casual users are definitly not going to dive into force flags for their browser. In 2011, we already had Unreal running on the browser thanks Crossbridge adobe-flash.github.io/crossbridge/ youtube.com/watch?v=13F3mKjsHoc And the 3D API was relatively good, help.adobe.com/en_US/FlashPlatform/refe…... And then there is the apparently safe WebAssembly, reason to kill Flash, "Everything Old is New Again: Binary Security of WebAssembly" usenix.org/conference/usenixsecurity20…... "WASM JIT pages are RWX for performance reasons making them easy to exploit" twitter.com/spoofyroot/status/137991178… More will come now that security researchers are starting to look into it.