Memory Safe Languages in Android 13
I am not a Rust or C++ fanboy, and I am happy that we are moving towards a future where there are less memory bugs, but… are we really?<p>- <a href="https:&#x2F;&#x2F;www.infoq.com&#x2F;news&#x2F;2021&#x2F;11&#x2F;rudra-rust-safety&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.infoq.com&#x2F;news&#x2F;2021&#x2F;11&#x2F;rudra-rust-safety&#x2F;</a><p>- <a href="https:&#x2F;&#x2F;cve.report&#x2F;vendor&#x2F;rust-lang" rel="nofollow">https:&#x2F;&#x2F;cve.report&#x2F;vendor&#x2F;rust-lang</a><p>And you can find online similar links and research on the topic.<p>All it takes is that you use that specific piece of code at the wrong time, and that’s it: your system which you once believed to be safe is not anymore safe. And you know what? You don’t even know what a sanitizer is, because they told you that Rust is a memory safe language and you don’t need anything else than the rust compiler - this is how I find 99% of today’s articles about Rust.<p>Sure, today being Rust less used than C&#x2F;C++ will clearly show less CVEs.<p>The question is … once it’s in the wild (and by this I mean “major” libs or serious shit done in Rust) how can you prevent such bugs without a runtime sanitizer?<p>Beware that such CVEs can affect Rust Standard library as well, not just an unknown library.<p>Again, there is no way of escaping bad programming and bad practices, no matter which language you use. Someone might argue that in Python or Java you can still do bad stuff, however, the likelihood is way lower, especially because most of your Java libraries will very likely be written in Java - unless you know it’s using JNI under the hood etc.