3 ms·
> "Mozilla confirmed the code exploited a critical memory management vulnerability in Firefox that was publicly reported on June 25, and is fixed in the latest
by yapcguy 13y ago
> "Mozilla confirmed the code exploited a critical memory management vulnerability in Firefox that was publicly reported on June 25, and is fixed in the latest version of the browser."
Will Rust help eliminate the problem of buffer overflows and other memory related hacks?
- Moral_ 13y agoThis was actually a use after free vulnerability, not a buffer overflow.
- lambda 13y agoWhich Rust should help with as well, as long as people don't use unsafe pointers too much. Of course, this is assuming Rust and Servo ever gain enough traction to build a viable browser; they're still at an early enough stage to be vulnerable to the problems lots of young, ambitious projects have, of taking on too much at once to ever be done enough for production use, interest petering out and never quite getting to the point of something widely usable (like Perl 6).
- pcwalton 13y agoIs it intended to? Yes. Will it? Time will tell. :)
- olsonjeffery 13y agoIIRC the original attack was a JS heap spray (using JavaScript Typed Arrays, no less), so not only would the browser have to be written in rust, but also the JavaScript engine which, AFAIK, isn't on Mozilla's roadmap (but I don't speak for them).
- khuey 13y agoUh, no. A heap spray is not an attack. It's a method of exploiting a vulnerability, but it's a) trivial to do and b) useless without said vuln. Also rewriting the JS engine in Rust doesn't change the ability to heap spray.