> Half of the known exploitable bugs in Chrome are use-after-frees > graph showing that 90% of high-severity bugs in the "Browser" part of the Chromium code ar

> Half of the known exploitable bugs in Chrome are use-after-frees > graph showing that 90% of high-severity bugs in the "Browser" part of the Chromium code are memory safety errors I'm going to bite the bullet here and mention the elephant in the room: the vast majority of these errors are virtually absent from Rust codebases. Logic errors happen in every language, but as the article shows, the majority of safety exploits come from memory safety errors, not logic errors, and memory-safe languages exist. I realize that Chromium is a pretty big codebase and they're not going to just switch to a different language, but at some point I feel like we should be acknowledging that maintaining a large-scale C++ codebase in a domain where exploits are highly sought by intelligence agencies is extremely unsafe, and solutions like this are just another layer of band-aids. (Though, to be clear, the amount of effort Google poured into defense-in-depth for Chromium and achieving an acceptable level of safety in practice is nothing short of amazing)