|
|
|
|
|
by tptacek
4148 days ago
|
|
It's a bit tautological to suggest that fixing the most common RCE flaws in C/C++ programs by replacing the language is the same as fixing all of the most common RCE flaws. The clear point here is that memory corruption is an affliction of C/C++ programs, but that other languages have other RCE-breeding flaws. |
|
Eval()/dynamic loading and little custom languages (like perhaps some "business rules" type systems) probably aren't as common in C/C++ eh?
Same for overzealous serialization systems (like Ruby's YAML issues, and I think .NET's binary serialization)?
What other kinds of things lead to RCE that don't or rarely occur in C/C++?