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.

Attacks/Breaches

8/10/2009
06:12 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Denial-Of-Service Attacks Hard To Kill

While tweets went silent last week, hundreds of other DDoS attacks were under way around the globe -- and several more powerful ones

Turns out Twitter, Facebook, and LiveJournal weren't the only sites hit hard by major distributed denial-of-service (DDoS) attacks late last week, and their attacks definitely weren't the biggest: More than 770 different DDoSes were spotted across the globe last Thursday.

One DDoS attack that took out a 3G mobile operator in Asia's Web portal was a powerful, 30 gigabit-per-second one, according to Craig Labovitz, chief scientist at Arbor Networks, who has been tracking the recent trends in DDoS attacks. The 30-Gbps DDoS was unusually potent; most attacks average about 1 Gbps or less, according to Arbor.

"There are hundreds of DDoS attacks any given day," Labovitz says.

Lately it seems to be the year of the DDoS, starting wtih the series of DDoS attacks in early July on high-profile U.S. federal government Websites, as well as South Korean targets. The good news is that researchers say, so far, there's no sign that the attacks on government sites were any more than disruption tactics, rather than a DDoS masking a more nefarious type of attack.

Then last week, the Twitterverse suffered tweet withdrawal on when Twitter was knocked offline for several hours by an apparent targeted DDoS attack aimed at a pro-Georgian blogger with accounts on Twitter, Facebook, and LiveJournal. But while the DDoS grabbed the attention of mainstream media and users, it was really just one of hundreds of these attacks that occur each day.

DDoS attacks aren't sophisticated, nor are they stealthy. And most of the time, they're basically just used as short-term disruption attacks for protest purposes or, sometimes, extortion. "I've been looking at these [DDoS] attacks for 10 years. It's odd that 10 years later, we're still dealing with this problem," says Jose Nazario, manager of security research for Arbor. "But it's really easy to [launch] these kinds of attacks."

As a matter of fact, it's cheaper to build out a botnet to wage DDoS attacks than it is to beef up your infrastructure with the appropriate redundancy and capacity to defend against one, Nazario says. "Configuring these devices [to combat a DDoS] is a big challenge," he says. "We have tools [out there] to defend, but they are not as cheap as running a botnet is."

Joe Stewart, director of malware research for SecureWorks, says DDoS attacks really haven't evolved much. "It's the same old DDoS botnet tools that have been around forever. They haven't really developed into anything more than we saw a few years ago in terms of they're throwing at Websites," Stewart says.

But botnet operators who DDoS have plenty of unknowing and willing recruits they can use to flood Websites with bogus traffic. And it's difficult for researchers and investigators to root out the actual botnet behind a DDoS. "We try to help out and identify some of these botnets. But a lot of times, it's [the attack] over before we can even start marshaling all of this data together and figure out where the attacks are coming from," Stewart says.

And DDoS attacks typically aren't waged from the world's biggest botnets -- the hundreds of thousands-strong spamming zombie armies that are known for traditional spam, Trojans, and in some cases, identity theft. The July attacks that hit the feds and South Korea, for instance, came from a botnet of about 35,000to 40,000 bots, SecureWorks' Stewart says. He says there are more than 1,000 botnets in reserve just waiting to DDoS. "Some are there because someone likes to wreak havoc on some IRC [Internet Relay Chat] network," he says. "A lot sit around idle."

Stewart says when he picks apart the botnets behind a DDoS, he usually finds evidence that these attackers regularly wage DDoSes. "It's obvious that these people are doing this daily...and their biz and picking out sites to extort money from, or they are or mad at someone, or [targeting] a competitor. They just launch these attacks all the time."

And according to Arbor, many of these attacks go unreported.

The 100,000 to 300,000-strong spamming botnets, meanwhile, are typically reserved for more lucrative malware and spam-spreading campaigns, SecureWorks' Stewart says.

And it's a good thing they aren't DDoS'ing, he says: "I'm not sure whose architecture could withstand a sustained attack from one of those 100,000- to 300,000-sized botnets," he says.

It used to be that DDoS attacks were all about size and flooding a router or sapping bandwidth, but that is changing, notes Arbor's Labovitz. "Now they are more focused on services and applications," he says.

Either way, DDoS attacks aren't going away, experts say. And the potential volume of these attacks on a day like last Thursday just shows how the Internet can't really be protected from them, SecureWorks' Stewart says.

"It's not possible today to prevent or eliminate DDoS attacks," he says. "We can do a better job of trying to trace them back to the source and being more cooperative among different countries in going after the people launching these attacks. But some attacks are rumored to be state-sponsored: then what do you do?

"There's just no way to make DDoS go away," he says. "We're going see these attacks continue to be effective."

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.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. 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
For Cybersecurity to Be Proactive, Terrains Must Be Mapped
Craig Harber, Chief Technology Officer at Fidelis Cybersecurity,  10/8/2019
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17545
PUBLISHED: 2019-10-14
GDAL through 3.0.1 has a poolDestroy double free in OGRExpatRealloc in ogr/ogr_expat.cpp when the 10MB threshold is exceeded.
CVE-2019-17546
PUBLISHED: 2019-10-14
tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer overflow via a crafted RGBA image, related to a "Negative-size-param" condition.
CVE-2019-17547
PUBLISHED: 2019-10-14
In ImageMagick before 7.0.8-62, TraceBezier in MagickCore/draw.c has a use-after-free.
CVE-2019-17501
PUBLISHED: 2019-10-14
Centreon 19.04 allows attackers to execute arbitrary OS commands via the Command Line field of main.php?p=60807&type=4 (aka the Configuration > Commands > Discovery screen).
CVE-2019-17539
PUBLISHED: 2019-10-14
In FFmpeg before 4.2, avcodec_open2 in libavcodec/utils.c allows a NULL pointer dereference and possibly unspecified other impact when there is no valid close function pointer.