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.

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
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-34491
PUBLISHED: 2022-06-25
In the RSS extension for MediaWiki through 1.38.1, when the $wgRSSAllowLinkTag config variable was set to true, and a new RSS feed was created with certain XSS payloads within its description tags and added to the $wgRSSUrlWhitelist config variable, stored XSS could occur via MediaWiki's template sy...
CVE-2022-29931
PUBLISHED: 2022-06-25
Raytion 7.2.0 allows reflected Cross-site Scripting (XSS).
CVE-2022-31017
PUBLISHED: 2022-06-25
Zulip is an open-source team collaboration tool. Versions 2.1.0 through and including 5.2 are vulnerable to a logic error. A stream configured as private with protected history, where new subscribers should not be allowed to see messages sent before they were subscribed, when edited causes the serve...
CVE-2022-31016
PUBLISHED: 2022-06-25
Argo CD is a declarative continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated A...
CVE-2022-24893
PUBLISHED: 2022-06-25
ESP-IDF is the official development framework for Espressif SoCs. In Espressif’s Bluetooth Mesh SDK (`ESP-BLE-MESH`), a memory corruption vulnerability can be triggered during provisioning, because there is no check for the `SegN` field of the Transaction Start PDU. This can resul...