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
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?