Post #1091174
2026-04-11 04:26 UTC
When I check CVEs most of the time it's memory safety related problems use after free and bounds checking. And this happens way too often especially in big projects like firefox or firefox based browsers. So many of those vulnerabilities could be fixed simply by using Rust. I think it makes sense to rewrite some things in Rust. While not perfect it could help avoid so many of those which happen way too often. Though sometimes it goes too far like we get a rust rewrite for a tiny program that didn't even need one, but I would say for big projects, using Rust makes a lot of sense.
Replies (1)
-
@Suiseiseki@freesoftwareextremist.com 2026-04-12 10:37
@squid64 Firefox uses Rust. Use after free and bounds checking are often the only bugs left is well developed GNU C projects and well that's a simple matter of fixing the mistake and the bug is fixed. Using Rust for a big project will result in exponentially more security issues than using GNU C, as the more syntactical tokens required to implement certain functionality, the greater the number of bugs you have. Remember that most bugs are logic bugs - not memory bugs. Memory bugs are easy to find and fix, while logic bugs are not. The borrow checker in Rust pretty much forces the programmer to implement logic bugs - but the resulting program is so complicated, it's very difficult to find them.