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.

Vulnerabilities / Threats

9/8/2013
05:32 PM
Mike Rothman
Mike Rothman
Commentary
50%
50%

Yet Another Reason To Hate Online Ads

Through the magic of JavaScript and ad networks, research presented at Black Hat by Jeremiah Grossman and Matt Johansen shows how to build a huge botnet quickly -- and then the fun begins

I'll readily admit I'm numb to advertising -- at least when I'm online. Ads are everywhere, taking up every visual inch of screen real estate, with the exception of the text I'm looking at. But I just focus on the text I'm looking for, so the rest of the stuff is noise. It's a bit different with TV since the magic of the DVR allows me to skip pretty much all of the ads. When I'm on the road and not using a DVR, I realize the true annoyance of these TV ads. In fact, I don't really watch TV without a DVR, with the exception of live sports. And in that case, the commercials annoy me.

But that's just annoyance, right? You can tune out the ads. Or check your Twitter or Facebook for two or three minutes while you learn about the latest magic pills to cure insomnia, frequent urination, or erectile dysfunction. (As an aside, if anyone has a good way to describe erectile dysfunction to a 10-year-old, I'm all ears. It's just a matter of time before I'm watching a football game with my kids and one of those ads show up.)

Yet at Black Hat, my friends Jeremiah Grossman and Matt Johansen showed that online advertising networks can be manipulated and gamed by attackers using pretty simple tactics to launch an attack (typically DDoS) against a specific site without any effort from the user. All they have to do is render a Web page with the attack ad embedded. We've spent years talking about not clicking on strange links or not going to those sites. But that's about not being in a bad neighborhood. What if the bad neighborhood comes to you?

That's right: If an advertising network accepts a compromised ad, likely paid for with a stolen credit card, it will display the ad almost anywhere on legitimate sites. There isn't much the website can do -- it has outsourced the ads to the ad network. The ad networks should have better controls, but well, you know. It's basically a drive-by attack that you can't really block. Render the legitimate page and get owned. That's awesome, right?

As Jeremiah and Matt described during their session, "Networks that serve up advertisements on ad-supported sites across the Internet frequently allow their advertisers to run arbitrary JavaScript on browsers displaying their ads." This JavaScript (if the browser is set to run JavaScript, which is the default mode) can have the browser make a request to the target, start a drive-by malware download, or lots of other diabolical stuff.

Even better, the pair of researchers got around an ad network's typical need to approve every change to an ad (for instance, changing the target) by referring to an external site to download the target URL or any other instructions in real time. JavaScript for the win. This gives an attacker the ability to dynamically change anything pertaining to the attack at will.

I know this is the "vulnerabilities and threats" section, and I don't necessarily need to suggest some ways to deal with this kind of attack. But that's not how I roll. So here are a few not-so-simple things you can do to protect the devices from this kind of activity. First, you can implement advanced malware protection on the endpoint devices, as I described in "Controlling the Big 7." This doesn't really help if the ad just gets the device to render a website (for DDoS purposes), but it can stop other compromises targeting the endpoint device.

Next is to address the traffic by blocking it on the network. Maybe you tighten the egress filtering policies on your egress NGFW, IPS, or Web filter looking for traffic bursts to a specific site. Or perhaps you implement a pretty tight device firewall policy to block outbound Web traffic unless it's approved. I use a tool called Little Snitch, which does this. It's a great tool, but it's a pain. The user would need to be sophisticated enough to realize an outbound connection request is no bueno and to deny it.

Or you can do what most folks will do -- ignore the problem. I mean, maybe it consumes a little Internet bandwidth with some of your devices pounding an unsuspecting website. But, ultimately, that isn't really going to impact much of anything from the standpoint of the success factors of either security or operations. There's the rub. These folks have no incentive to deal with this issue, so they won't.

And the attackers will run to the bank. Again.

Mike Rothman is President of Securosis and author of the Pragmatic CSO

Mike's bold perspectives and irreverent style are invaluable as companies determine effective strategies to grapple with the dynamic security threatscape. Mike specializes in the sexy aspects of security, like protecting networks and endpoints, security management, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tayloradvantage
50%
50%
tayloradvantage,
User Rank: Apprentice
11/21/2013 | 1:48:09 AM
re: Yet Another Reason To Hate Online Ads
I wonder if the use of an ad blocker like the one at https://adblockplus.org can mitigate this too.
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
7 SMB Security Tips That Will Keep Your Company Safe
Steve Zurier, Contributing Writer,  10/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: The old using of sock puppets for Shoulder Surfing technique. 
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-17513
PUBLISHED: 2019-10-18
An issue was discovered in Ratpack before 1.7.5. Due to a misuse of the Netty library class DefaultHttpHeaders, there is no validation that headers lack HTTP control characters. Thus, if untrusted data is used to construct HTTP headers with Ratpack, HTTP Response Splitting can occur.
CVE-2019-8216
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure .
CVE-2019-8217
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-8218
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure .
CVE-2019-8219
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .