Welcome Guest. | Log In| Register | Membership Benefits
Dark Reading's hacked-off Weblog

Topics:   Hacked Off
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

When Mass SQL Injection Worms Evolve...Again

In the past, I've described how mass SQL injection worms took the Web completely by storm. Two years ago, SQL injection attacks evolved from sentient, one-off, targeted data-stealing exploits, like in the breaches at Hannaford Brothers and Heartland, to fully automated, unauthenticated mass-scale Website malware-injecting robots. The robots' mission, rather than extracting sensitive data, is implanting malware-laced iFrames into back-end databases where they are later served up to unsuspecting Web visitors as content. And they've been extremely successful.

Aug 24, 2009 | 07:33 PM | 

By Jeremiah Grossman
Dark Reading
In the past, I've described how mass SQL injection worms took the Web completely by storm. Two years ago, SQL injection attacks evolved from sentient, one-off, targeted data-stealing exploits, like in the breaches at Hannaford Brothers and Heartland, to fully automated, unauthenticated mass-scale Website malware-injecting robots. The robots' mission, rather than extracting sensitive data, is implanting malware-laced iFrames into back-end databases where they are later served up to unsuspecting Web visitors as content. And they've been extremely successful.According to Websense, 70 percent of the top 100 popular Websites either have hosted malicious content or redirected unsuspecting victims to malicious sites. If a user's machine gets a virus/worm, chances are the infection originated from some Web page.

As bad as things are now, we could be due for another evolution.

Some of the first evolutions we saw in mass SQL injection worms was their ability to disguise their payload from intrusion detection systems, Web application firewalls, and other application input validation routines. Clever encoding schemes helped bypass security controls, and funneling attacks over HTTP POST would hamper exploit logging and forensics.

The good news is that today's mass SQL injection attacks are NOT scanning while authenticated: They don't register accounts, and they don't log in (username/password), so they can't see or exploit any Website functionality with those preconditions. Basically, none of the Deep Web is touched. Only the functionality wide open to the public is within scope, leaving out a ton of Websites and attack surface. But what if mass SQL injection worms evolved again? What if they found a generic way to log in?

At first, that concept sounded rather remote. I mean, talk about some serious AI. Not even Google can do this kind of Deep Web crawling capability (at least I don't think so). Consider that the worms would first need to figure out that they needed to register an account, then find and fill out the registration form with valid data (including CAPTCHA), potentially activate their accounts via email, log-in with their username/password, and then finally start attacking the Website. The more I broke down the requirements, the more feasible this sounded.

Personal experience and cursory research reveals that Web spammers already know how to fingerprint popular blogging systems, message boards, and Web mail providers. Spammers are completely capable of automatically registering accounts, bypassing CAPTCHA protection, responding to activation email, logging-in, and spamming the hell out of us. We've all seen the crappy backlinks, malware URLs, and other spammy messages. But again, these activities are fairly limited to well-known platforms.

What Web spammers don't do, to my knowledge, is how to use this capability to perform SQL injection attacks post-login. So we're left to speculate: How hard would it really be for them to make these technology pieces more generic? All the pieces of the puzzle seem possible, perhaps already built, just not yet culled together. We also don't know when, if ever, this evolution might take place.

Are we ready if it does? Some are. But the rest are going to have a really bad year.

Jeremiah Grossman is CTO and founder of WhiteHat Security. Special to Dark Reading



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









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
  May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008