Welcome Guest. | Log In | Register | Membership Benefits

DHS, Mitre Name SQL Injection Flaws As Most Dangerous Software Error

Top 25 list also cites OS command errors, buffer overflow vulns at top of list

Jun 29, 2011 | 07:12 PM | 

By Tim Wilson

Vulnerabilities that leave applications open to SQL injection are the most dangerous software errors in cyberspace, according to rankings issued earlier this week by top security groups.

Issued by the Department of Homeland Security, Mitre, and the SANS Institute, the "2011 CWE/SANS Top 25 Most Dangerous Software Errors" is a list of the most widespread and critical errors that can lead to serious vulnerabilities in software.

"They are often easy to find, and easy to exploit," the groups say. "They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or prevent the software from working at all."

The Top 25 list is an extension of a list that has been issued in the past by Mitre and the SANS Institute to help programmers to prevent the kinds of vulnerabilities that often lead to application breaches -- data on more than 800 programming errors, design errors, and architecture errors that can lead to exploitable vulnerabilities. The list was selected from more than 800 errors recorded in Mitre's Common Weakness Enumeration (CWE) database.

This year's Top 25 entries are prioritized using inputs from more than 20 different organizations, which evaluated each weakness based on prevalence, importance, and likelihood of exploit. It uses the Common Weakness Scoring System (CWSS) to score and rank the final results.

Operating-system command injection finished second on the "most dangerous" list, followed by buffer overflow and cross-site scripting.

One purpose of the list is to give weight to specific flaws, in hopes of driving programmers to avoid them, says Alan Paller, director of the SANS Institute. "It helps to show that some errors have a high value and some have low value," Paller says. "You can't give a programmer a list of 860 things that need to be fixed and expect them to respond. They'll throw the list away. You need to give them some weight."

Application security experts say the list helps raise consciousness on specific types of errors, but they wonder how much impact it will likely have on software developers.

"Everyone seems to be focusing on the fact that SQL injection made it to No. 1 this year, but I find myself thinking, 'So what?'" says Vinnie Liu, a founder of the consulting firm Stach & Liu, which offers application assessment and testing services. "SQL injection was the vulnerability behind the Sony, Infraguard, and other recent attacks. Yet no matter if it’s No. 1, No. 4, or No. 10, it always has been one of the primary causes of significant data breaches in the past, and it will continue to be for many years to come." Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports