Yesterday's SQL worms, today's problem
For the last few weeks I have been watching old versions of SQL attacks, worms
and probes continue to circulate around the Internet. For a year or so now,
I have continued to be fascinated by the life span of old attacks and worms.
The thing about these SQL worms is that their traffic is so large, even today.
According to popular sources like ATLAS, they represent nearly 70% of all malicious
traffic on the Internet today. 70% is a large number, especially for vulnerabilities
that date back to 2002. Here we are
more than 5 years later and these threats are still propagating!
Our HoneyPoints often detect Slammer worm activity and illicit SQL probes from
the Internet. These probes originate from all around the world and no particular
region seems to emerge as the most common.
But what of targets? Our assessment technicians say they almost never run into
one in corporate environments today. I suppose that they still exist in more
than a few cable modem or other systems without proper firewalls, but certainly
the availability of SQL services to the raw Internet has to have dwindled to
almost none. If that is true, then why all the scanning activity?
I have made a few attempts to backtrack hosts that perform the scans and at
first blush many show the signs of common botnet infections. Most are not running
exposed SQL themselves, so that means that the code has likely been implemented
into many bot-net exploitation frameworks. Perhaps the bot masters have the
idea that when they infiltrate a commercial network, the SQL exploits will be
available and useful to them? My assessment team says this is pretty true. Even
today, they find blank sa passwords and other age-old SQL issues
inside major corporate clients. So perhaps, that is why these old exploits continue
to thrive.
In either case, significant efforts should be made to reduce or eliminate these
older vulnerabilities and to remove them from our current threats
that we face today. So long as we have this noisy attack traffic from the past
circulating, it makes it even harder for us to focus on emerging threats and
risks that affect our Internet facing systems today.
MicroSolved, Inc.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.













