Re:Actively exploited sandbox RCE in all Chromium versions
by rvz on Saturday September 05, 2026 @09:56AM
(#49576551)
Exactly this. This is a never ending problem with C/C++ and it's these same memory corruption CVEs appearing all the time.
I also cringe at projects that "compile C to WASM" and then believe that it is immediately "memory-safe". (It really is not.)
The only exception for C/C++ projects is Fil-C which that is memory-safe. New projects at this point should just consider using Rust instead.
Re:Actively exploited sandbox RCE in all Chromium versions
by tsoukase on Sunday September 06, 2026 @11:17AM
(#49587321)
I believe programmers still write in C(++) after memory safe options, in order to continue being occupied afterwards, fixing the bugs that will arise. Without criminals, police is obsolete.
Yes, if your JavaScript engine is written in C++, it’s going to be very hard to avoid very gross bugs. We have better options now.
The ability of adversaries to find and exploit very gross bugs in C++ codebases should have already compelled the industry to move to memory safety. Now that AI has democratized the ability to scour C++ codebases for really gross and exploitable bugs, I should think that our hands are at last being forced. I’m not impressed by what I’ve seen in the industry with respect to taking memory safety seriously.