Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

9/2/2010
03:06 PM
100%
0%

Five Ways To Stop Mass SQL Injection Attacks

The best practices for mitigating this popular form of attack often are not being deployed

A new wave of mass SQL injection attacks seen in mid-August to hit over half a million websites, including parts of Apple's site serves as a weighty reminder of the growing prevalence of mass injections and of SQL injections in general as a favorite means of hackers to tap into organizations' infrastructure and data resources.

In light of these attacks, security researchers believe now is as good of a time as any to revisit some best practices necessary to prevent mass SQL injections and mitigate the risks associated with injection attacks. These practices are hardly revolutionary, but it is clear that they aren't being implemented as widely as they need to be.

"You keep seeing the same issues come up over and over again for many years now," says Alex Rothacker, manager of Team SHATTER, Application Security Inc.'s research arm. "Even with this Apple attack, they used a little bit more advanced attacks, but still it's stuff that's been talked about at Black Hat for two years now."

1. Never trust input.

This should be one of the mantras of developers as they write Web application code. According to Jacob West, security research director for Fortify Security, organizations should "create and enforce secure coding guidelines for software developed in-house that requires SQL be constructed using parameterized queries, which prevent SQL injection attacks by differentiating code from data."

Developers should work to ensure that inputs are sanitized before querying the database, Rothacker says. "Make sure that the data that people input into your website is exactly the data you're looking for, so if you're asking for a social security number, you want to make sure it is actually a social security number and there are no letters in there," he says.

2. Implement filtering and monitoring tools.

Filtering and monitoring tools at the Web application and database levels will help block attacks and detect attack behavior in order to mitigate risk of exposure to mass SQL injection attacks.

At the application level, West says that organizations should "wear suspenders," by implementing runtime security monitoring to defend against SQL injection attacks and vulnerabilities in production systems. Similarly, Web application firewalls can help organizations put certain behavior-based rule sets in place to block attacks before they do damage.

On the database, database activity monitoring can also filter attacks from the back end, Rothacker says. "Database activity monitoring is a really great tool against SQL injections," he explains. "For known injection attacks, there's always filters out there that will help alert the DBAs that something bad is going on and there's also some pretty generic filters that look for things that are very typical in SQL injections -- things like an uneven number of quotes that break up the SQL code and stuff like that."

3. Craft error messages carefully.

Hackers can and will use your own error messages against you to better dial in future attacks. That's why both the development team and DBAs need to think about the error messages they're returning when users input something unexpected.

"[Organizations should] configure the Web and database servers to not output error or warning messages," warns Neil Daswani, co-founder and CTO of Dasient. "Attackers can use such messages to learn about your database schema using techniques such as 'blind SQL injection.'"

4. Patch and harden databases.

The risks associated with SQL injections are escalated when the databases tied to the Web applications under attack are weak due to poor patching and configuration.

"Keep your databases patched, and also your Web applications and Web services while you're at it," says Rothacker. "I think that should be a no-brainer."

Additionally, don't forget about how your databases are configured. "Harden the database and the operating system of the machine it is running on by disabling unnecessary services and functionality," says Dasient's Daswani.

5. Limit database privileges.

Finally, organizations need to do a better job at managing how accounts associated with Web applications are interacting with back-end databases. Many problems arise due to DBAs giving carte blanche to these accounts in order to make developers' lives easier. But these super accounts are very vulnerable to attack and greatly broaden the risks to databases posed by SQL injection and other Web app-based attacks.

"You definitely want to run all of these accounts that serve as a Web account that have access to the back-end database at really low privileges so that they can really only access the data that they're supposed to access," Rothacker says. "You want to make sure they don't have any rights to make changes on the database."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
JoePorter
50%
50%
JoePorter,
User Rank: Apprentice
2/8/2013 | 12:11:36 AM
re: Five Ways To Stop Mass SQL Injection Attacks
Fantastic post!

Another one I found quite simply explained is here:

http://www.programmerinterview...
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/1/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19393
PUBLISHED: 2020-10-01
The Web application on Rittal CMC PU III 7030.000 V3.00 V3.11.00_2 to V3.15.70_4 devices fails to sanitize user input on the system configurations page. This allows an attacker to backdoor the device with HTML and browser-interpreted content (such as JavaScript or other client-side scripts) as the c...
CVE-2020-16844
PUBLISHED: 2020-10-01
In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy.
CVE-2020-24620
PUBLISHED: 2020-10-01
Unisys Stealth(core) before 4.0.132 stores Passwords in a Recoverable Format.
CVE-2020-25017
PUBLISHED: 2020-10-01
Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.
CVE-2020-25018
PUBLISHED: 2020-10-01
Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization.