Top 25 Most Dangerous Programming Errors, should developers be liable?
March 5, 2010 by Ayo Akinyemi · Leave a Comment
Programming gaffes are bound to occur. Whether it is a minor issue, which leads to a temporary collapse of the software system or a major one, that allows for a cyberattack, should vendors be liable for these flaws after delivering a code that gets a nod when tested?
Customers want products, they want it fast, they also want it cheap. If developers are to avoid these security loop holes, engage in a liability project, and provide a clean software, it would lead to more
expensive software. How can we tackle this issue?
[1] Failure to Preserve Web Page Structure (‘Cross-site Scripting’)
[2] Improper Sanitization of Special Elements used in an SQL Command (‘SQL Injection’)
[3] Buffer Copy without Checking Size of Input (‘Classic Buffer Overflow’)
[4] Cross-Site Request Forgery (CSRF)
[5] Improper Access Control (Authorization)
Complete list of 25 at http://cwe.mitre.org/top25/
