Perimeter
8/1/2011
02:09 PM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

WAFs And SQL Injection

WAFs protect databases from SQL injection for only so long

The ModSecurity site is putting on the SQL Injection Challenge. Contestants are attempting to find successful SQL injection attacks against target applications. The four sample applications are from IBM, Cenzic, HP, and Acunetix, each with a slightly different host configuration and database platform.

There are two contests within the challenge. The first test is a timed event to see who can detect the database, table, and column names behind test applications. The second test is to find a vulnerability and avoid both inbound attacks and data extrusion detection. These applications have been previously scanned for common vulnerabilities and injection attacks, and there are active Web application firewalls running.

Remember that SQL injection is an attack on a database that goes through a firewall, an application, and, in some cases, a supporting Web application firewall as well. What's also important to note here is that these "test" applications are set up to be pretty secure.

The first phase of the event has been completed, and each of the platforms were successfully compromised. On average, it took 72 hours for an attacker to break in across the various contests and against each of the four applications. The test results demonstrate that a Web application firewall (WAF) will be breached by a persistent attacker. It's not a matter of if -- it's a matter of when. The real value of WAF technology is to monitor and detect attacks so you respond to the attack. That might mean updating your WAF rules, filtering some inbound connections, double-checking that input values are properly filtered, or even taking some of your services off line.

There are a few lessons to learn here, but paramount is that you need to be monitoring activity -- and actually reviewing the logs -- if you hope to catch and react to an attack. Static defenses only last so long.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6213
Published: 2014-04-19
Unspecified vulnerability in Virtual User Generator in HP LoadRunner before 11.52 Patch 1 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1833.

CVE-2013-6214
Published: 2014-04-19
Unspecified vulnerability in the Integration Service in HP Universal Configuration Management Database 9.05, 10.01, and 10.10 allows remote authenticated users to obtain sensitive information via unknown vectors, aka ZDI-CAN-2042.

CVE-2012-0871
Published: 2014-04-18
The session_link_x11_socket function in login/logind-session.c in systemd-logind in systemd, possibly 37 and earlier, allows local users to create or overwrite arbitrary files via a symlink attack on the X11 user directory in /run/user/.

CVE-2012-6646
Published: 2014-04-18
F-Secure Anti-Virus, Safe Anywhere, and PSB Workstation Security before 11500 for Mac OS X allows local users to disable the Mac OS X firewall via unspecified vectors.

CVE-2013-4279
Published: 2014-04-18
imapsync 1.564 and earlier performs a release check by default, which sends sensitive information (imapsync, operating system, and Perl version) to the developer's site.

Best of the Web