Vulnerabilities / Threats

5/18/2010
05:39 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Dasient Helps Publishers Stop Malicious Ads

The start-up's anti-malvertising service promises better tools for dealing with infected ads.

Dasient, a Palo Alto, Calif.-based security start-up, on Tuesday introduced a new service to protect publishers and advertising networks from malicious online ads.

Malicious online advertising, or malvertising, involves the insertion of infected ad files into ad networks. Viewers of the the malicious ads are at risk of having their computers compromised by a drive-by-downloads or of being presented with a fake antivirus scam.

Malvertising compounds the problems of malware -- identity theft, fraud, and loss of privacy -- by damaging the brands of the publishers and ad networks that inadvertently deliver infected ads.

In early 2008, Niels Provos, a security engineer at Google, said in a blog post that about 2% of malicious Web sites were distributing malware through advertising, based on an analysis of about 2,000 known advertising networks.

The problem posed by malvertising was bad enough to prompt Google last summer to launch a search site called Anti-Malvertising.com to help its ad network partners fight malvertising. And Microsoft in September last year filed five lawsuits to halt the distribution of malicious ads through its online ad platform, Microsoft AdManager.

Dasient co-founder Neil Daswani, a former Google engineer, estimates that close to 1.3 million malicious ads are served every day. Such ads tend to persist for about a week before being removed, a result of the tendency of malware creators to release malicious ads over the weekend, when there's often no ad network staff around to field complaints or detect the infected files.

Dasient's answer to the problem, fittingly enough, is called Anti-Malvertising Solution (AMS). The service monitors ad networks for malicious files and automatically notifies ad network partners when malvertisements are detected. It provides a way to block malicious ads immediately and documents the information needed to remove them.

Daswani says that its better for publishers and ad networks to address the problem than to leave it up to Internet users, who might choose to block ads as a security measure.

"Advertising to an extent has funded the generation of content on the Web," he said. "As an industry, it would be disappointing if things got so bad that people shut off ads."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Ericka Chickowski, Contributing Writer, Dark Reading,  5/15/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "Security through obscurity"
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2607
PUBLISHED: 2018-05-21
jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users...
CVE-2018-1108
PUBLISHED: 2018-05-21
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
CVE-2018-11330
PUBLISHED: 2018-05-21
An issue was discovered in Pluck before 4.7.6. There is authenticated stored XSS because the character set for filenames is not properly restricted.
CVE-2018-11331
PUBLISHED: 2018-05-21
An issue was discovered in Pluck before 4.7.6. Remote PHP code execution is possible because the set of disallowed filetypes for uploads in missing some applicable ones such as .phtml and .htaccess.
CVE-2018-7687
PUBLISHED: 2018-05-21
The Micro Focus Client for OES before version 2 SP4 IR8a has a vulnerability that could allow a local attacker to elevate privileges via a buffer overflow in ncfsd.sys.