4 ms·
It is nice if they can count. However instead of sending them back to kindergarten, it might make sense to find a compiler/language/framework that would make in
by rdtsc 12y ago
It is nice if they can count. However instead of sending them back to kindergarten, it might make sense to find a compiler/language/framework that would make inability to count not result in easy remote exploits.
- peterwwillis 12y agoSo remove the ability to use pointers to directly access memory. Then you're only left with all of the other security vulnerabilities found in every such language.
- pjmlp 12y agoIt would still be an improvement.
- AgentME 12y agoUh, how often do code execution vulnerabilities show up in non-C programs compared to how often they show up in C programs?
- Ded7xSEoPKYNsDd 12y agoAll the time: SQLi, XSS, arbitrary file upload, ...
- tedunangst 12y agoThe fun part is that when you find a language/framework that (e.g.) deserializes data by running eval(), it's so much easier to write portable exploits. 32 bit, 64 bit, x86, arm, mips, aslr? None of that matters. Literally eval(system("/bin/sh")) and done.
- MichaelGG 12y agoXSS is a totally different level. When's the last time a bunch of networked devices needed patches because of XSS? And even if these problems were as widespread, eliminating a huge class of errors is a big step up. Nearly every serious vulnerability in Microsoft's code for the past years is from memory unsafeness. Hell, why bother with malaria or smallpox vaccines, since people just die from something else anyways.
- peterwwillis 12y agoThe answer to your question is "all the time", because most new appliances are using more high level languages and xss-prone interfaces. This also ignores all the ones that don't get found/fixed. Of course we should work to eliminate problems, but you have to consider the bigger picture and whether abandoning the language is worth it. So far the pros outweigh the few unique cons.
- cm2187 12y agoWithout trolling, it is true that string manipulation has been a fertile source of major bugs. I don't really see the benefit of having to manipulate arrays of characters manually instead of a string datatype. An unmanaged language doesn't really gain anything from this, apart from this sort of embarrassment.