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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
The Truth About Malvertising
Newest First  |  Oldest First  |  Threaded View
PZav
PZav,
 User Rank: Author
1/21/2015 | 7:48:35 PM
Re: who is responsible? onus on advertisers and publishers
The reason ISPs won't get involved is because its a slippery slope for them. If they created controls for something like bad adverstisements, then media outlets would start putting pressure on them to curb pirating. Its the same issue for search engines. Plus there is the whole privacy can of worms as well. How closely do they have to look at our traffic to setup meaningful controls? As soon as they're viewed as anything more than a transit system, they begin to take on a lot more responsibility. Its too much of a liability.  
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
1/21/2015 | 8:48:34 AM
Re: who is responsible? onus on advertisers and publishers
It's hard to know who should take the lead for malvertising prevention -- or the blame for the problem in the first place. Yes, it's a consumer problem via personal computers. But so is a  lot of garden variety malware. Maybe ISPs should provide consumers with better controls ?
Chris Weltzien
Chris Weltzien,
 User Rank: Author
1/20/2015 | 5:31:59 PM
Re: who is responsible? onus on advertisers and publishers
This problem has been brewing for a while. We saw it back in 2007 at Exploit Prevention Labs when it was just starting to surface and when we uncovered some some malicious Google Ads campaigns USA Today ran an article on it. (can't link to it in comments)  More recently the Senate had hearings on it in the spring of 2014, where ad networks were called out for ignoring the problem. If you are looking to protect yourself AVG's LinkScanner is a real-time client side solution, if you are looking for someone to take responsibility I wouldn't hold your breath. 
PZav
PZav,
 User Rank: Author
1/20/2015 | 4:02:55 PM
Re: who is responsible? onus on advertisers and publishers
History is on your side Marilyn! I do wonder if this is recognized as a consumer facing problem, if brands will take it more seriously though. It seemed like with the POS breaches that the banks were really the ones left holding the bag. But malvertising reaches personal computers. Time will tell! Thanks for the comment.
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
1/20/2015 | 9:04:17 AM
Re: who is responsible? onus on advertisers and publishers
I wouldn't hold my breath for advertisers and publishers to be proactive about malvertising -- at least not any time soon. Retailers have certainly been a major target of attacks and look at their track record at getting ahead of the hackers...
PZav
PZav,
 User Rank: Author
1/19/2015 | 12:15:47 PM
Re: who is responsible?
Maybe one of the biggest concerns is the harm malvertising will cause to the Internet economy, which is fueled by digital advertising. 
macker490
macker490,
 User Rank: Ninja
1/17/2015 | 9:51:31 AM
who is responsible?
until the laws regarding product liability are changed the system owner is responsible.

I am considering running my browser in a "NamedSpace" such as "firejail"  -- as my response to this question.

 


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file