Home > slashdot > The 25 Most Dangerous Programming Errors

The 25 Most Dangerous Programming Errors

February 17th, 2010 02:55 admin Leave a comment Go to comments

Hugh Pickens writes “The Register reports that experts from some 30 organizations worldwide have compiled 2010′s list of the 25 most dangerous programming errors along with a novel way to prevent them: by drafting contracts that hold developers responsible when bugs creep into applications. The 25 flaws are the cause of almost every major cyber attack in recent history, including the ones that recently struck Google and 33 other large companies, as well as breaches suffered by military systems and millions of small business and home users. The top 25 entries are prioritized using inputs from over 20 different organizations, who evaluated each weakness based on prevalence and importance. Interestingly enough the classic buffer overflow ranked 3rd in the list while Cross-site Scripting and SQL Injection are considered the 1-2 punch of security weaknesses in 2010. Security experts say business customers have the means to foster safer products by demanding that vendors follow common-sense safety measures such as verifying that all team members successfully clear a background investigation and be trained in secure programming techniques. ‘As a customer, you have the power to influence vendors to provide more secure products by letting them know that security is important to you,’ the introduction to the list states and includes a draft contract with the terms customers should request to enable buyers of custom software to make code writers responsible for checking the code and for fixing security flaws before software is delivered.”

Source: The 25 Most Dangerous Programming Errors

Related Articles:

  1. The Most Dangerous Programming Mistakes
  2. Catching Satnav Errors On Google Street View
  3. Stuxnet Authors Made Key Errors
  4. London Stock Exchange Price Errors ‘Emerged At Linux Launch’
  5. When Is It Right To Go Public With Security Flaws?
blog comments powered by Disqus