Memory corruption is much harder (and in most cases realistically not at all) to exploit beyond a DoS, and that's what you would get with "safe" languages such as Rust or Python as well.
Heartbleed, Shellshock, Dirty COW etc. would all happen exactly the same way in different programming languages.
Yes, there is clearly a benefit in using something which makes it much harder introducing memory safety issues, but it's not nearly as big as many here on HN think.
I believe the same is true (roughly) with the Coinbase attack that went after Firefox.
In short, memory safety is not only responsible for the majority of reported vulns, but also the exploited ones, at least in the case of browsers.
> Heartbleed, Shellshock, Dirty COW etc. would all happen exactly the same way in different programming languages.
Heartbleed is impossible in a memory safe language, at the least. Same with cloudbleed for that matter.
DirtyCow and shellshock, sure.
It's a bit of a moot point though - human energy is finite, consider if we could spend energy on problems like DirtyCow and shellshock instead of memory safety issues that simply don't exist in many languages.
About 70% of CVE reported exploits are due to memory corruption.
Living with the remaining 30% would already be a huge security improvement.