Application Security // Database Security
4/17/2014
06:10 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
0%
100%

SQL Injection Cleanup Takes Two Months or More

A new report highlights the prevalence and persistence of SQL injection attacks.

In the past 12 months, 65% of organizations have suffered a SQL injection attack, and it took them close to 140 days to realize they had been hit.

According to a report by the Ponemon Institute published yesterday, it took an average of 68 days for victim organizations to recover and clean up after discovering they had suffered a SQL injection attack.

SQL injection is a hacking technique where an attacker exploits a vulnerability in the targeted application to send malicious SQL statements to the database. The attacker inserts malicious SQL statements into an entry field.

"SQL injection has been around for ages," says Larry Ponemon, chairman and founder of the Ponemon Institute. It just won't go away. "You're lucky if you discover it [quickly], and it takes a long time to remediate: 140 days for an organization to even detect a SQL injection attack" has occurred. "And 40% of them say it takes six months or longer to detect it... It's nine months on average from start to finish."

The report, was commissioned by DB Networks, is based on responses from 595 IT security professionals in the US, both in the commercial and government sectors.

More than half of the organizations neither test nor validate third-party software for SQL injection vulnerabilities, the survey found, and 56% say finding the source of SQL injection is harder due to the emergence of mobile devices at the office.

Other findings: Forty-four percent use professional penetration testers to look for bugs, while just 35% of those tests include looking for SQL injection bugs. More than half say they have or will begin to swap their signature-based security with behavioral analysis-based tools in the next 24 months. Half say they will use behavioral analysis tools to track database activity.

The good news is that more organizations are aware of SQL injection threats, according to Michael Sabo, director of marketing for DB Networks. "I'm excited to see at least these organizations realized the significance of the threat. SQL injection is always one of the top threats... This attack has become highly automated," he says.

A full copy of the report, The SQL Injection Threat Study, is available here (registration required).

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
4/21/2014 | 3:55:00 PM
Cost of SQL Injection cleanup?
Interesting data, Kelly. Wondering if the Ponemon study quantified any of the costs to organizations of a SQL injection attack, in terms of dollars and data loss. 
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4594
Published: 2014-10-25
The Payment for Webform module 7.x-1.x before 7.x-1.5 for Drupal does not restrict access by anonymous users, which allows remote anonymous users to use the payment of other anonymous users when submitting a form that requires payment.

CVE-2014-0476
Published: 2014-10-25
The slapper function in chkrootkit before 0.50 does not properly quote file paths, which allows local users to execute arbitrary code via a Trojan horse executable. NOTE: this is only a vulnerability when /tmp is not mounted with the noexec option.

CVE-2014-1927
Published: 2014-10-25
The shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "$(" command-substitution sequences, a different vulnerability than CVE-2014-1928....

CVE-2014-1928
Published: 2014-10-25
The shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "\" (backslash) characters to form multi-command sequences, a different vulner...

CVE-2014-1929
Published: 2014-10-25
python-gnupg 0.3.5 and 0.3.6 allows context-dependent attackers to have an unspecified impact via vectors related to "option injection through positional arguments." NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.