[josefx]

I heard they once created an entire language that would replace C++ in all their projects. Obviously they never rewrote Chrome in Go.

> 10s of billions are spent to try to get Chromium to not have these vulnerabilities, using those tools. And here we are.

Shouldn't pages run in isolated and sandboxed processes anyway? If that exploit gets you anywhere it would be a failure of multiple layers.

[stackghost]

They do run in a sandbox, and this exploit gives the attacker RCE inside the sandbox. It is not in and of itself a sandbox escape.

However if you have arbitrary code execution then you can groom the heap with malloc/new to create the layout for a heap overflow->ret2libc or something similar

[staticassertion]

The ITW exploit has some sort of sandbox escape. My money is on a kernel exploit, but there are other options - universal XSS, IPC, etc. Kernel vuln is most likely by far imo.

Chromium uses probably the single most advanced sandbox out there, at least for software that users are likely to run into.

[StilesCrisis]

I don't think Go was ever planned to completely overtake C++. It is still a garbage collected language at the end of the day.

[tgv]

I think the parent tries to refer to Carbon: https://en.wikipedia.org/wiki/Carbon_(programming_language)

[pjmlp]

Many people enjoy playing games, and video productions, written in a garbage collected C++ engine.

Go's main issue is its language design approach.