Cloud

11/9/2017
06:10 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

AV Vendors Have Immunity for Malware-Blocking Decisions, Court Says

Enigma Software Group had sued Malwarebytes for characterizing its anti-malware software as unsafe, but its case was dismissed.

Antivirus software vendor Malwarebytes successfully cited a rarely used provision in the Communications Decency Act of 1996 (CDA) to win dismissal of a lawsuit that accused the company of using its software to interfere with a rival's product.

Enigma Software Group (ESG), a provider of anti-malware tools, in October 2016 sued rival Malwarebytes for unlawfully characterizing Enigma's software as potentially harmful to users.

In its complaint, Enigma alleged that Malwarebytes's AV software was wrongly classifying Enigma's SpyHunter and RegHunter tools as potentially unwanted programs (aka PUPs) and either quarantining them or warning end users that the software posed a security threat to their systems.

Enigma claimed that Malwarebytes was trying to interfere with its client base in retaliation for a lawsuit that it had previously filed against Bleepingcomputer.com, a Malwarebytes affiliate. The vendor noted that Malwarebytes' software for 10 years previously had not identified either SpyHunter or RegHunter as unwanted software or malware.

Malwarebytes argued that its actions were protected under Section 230(c)(2)(B) of the CDA, which provides legal immunity to computer vendors that provide "technical means to restrict access" to obscene, lewd, excessively violent, and otherwise objectionable content.

Malwarebytes claimed that as provider of filtering tools for restricting access to items it deems as objectionable, the company had immunity under the Section 230 provision.

Federal Judge Edward Davila of the US District Court for the Northern District of California Tuesday agreed with Malwarebyte in dismissing Enigma's lawsuit. Judge Davila rejected Enigma's argument that the language in Section 230 does not apply to malware but to other types of objectionable content such as obscene, lewd, lascivious, and violent content.

He also noted that contrary to Engima's claims, the law indeed gives Malwarebytes the legal authority to decide what is "objectionable" material and filter it or warn users about it. The immunity offered under Section 230(c)(2)(B) is available to providers such as Malwarebytes regardless of whether they are acting in good faith or not when filtering objectionable content, Judge Davila noted in his 7-page decision.

The decision marks the second time in the last eight years that an anti-malware vendor has successfully used the CDA provision to overcome a similar legal challenge. The last time was in 2009, when Kaspersky Lab used the provision to overcome a lawsuit filed against it by Zango Inc.

"Since the Zango vs Kaspersky case, we have seen very few challenges to the antivirus, antispyware, and anti-spam industry," over how they filter out objectionable content, says Eric Goldman, a professor at the Santa Clara University School of Law.

Before that case, there was much agitation over lawsuits and threats to sue people in the anti-malware industry over their classification decisions, Goldman says. "It created a lot of stress among those vendors," he says.

On the one hand, they needed their tools to be robust enough to block malware threats, while on the other the vendors had to be extremely careful when classifying content as unwanted and objectionable. "They had to get it just right every time," he says.

The ruling in the Malwarebytes case is consistent with the ruling in the Kaspersky case, and is another rare example of the Section 230 provision being used successfully to litigate a case. A vast majority of the cases involving Section 230 disputes have to do with liability for hosting objectionable content, Goldman says.

Andy Serwin, co-chair of the privacy group at Morrison & Foerster, says this week's ruling in the dispute between Enigma and Malwarebytes does not surprise him. "This issue has been litigated before," with the same outcome, he says.

That does not mean that vendors such as Enigma have no recourse. Companies such as Malwarebytes have considerable immunity in such disputes. But third parties whose malware signature or other information that Malwarebytes or other anti-malware firms use for filtering decisions, may not always have that protection.

"This is not a situation where if there is a wrong, there is no remedy," at all Serwin notes. "It is just against whom that remedy is available."

Related Content:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Number of Retailers Impacted by Breaches Doubles
Ericka Chickowski, Contributing Writer, Dark Reading,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19990
PUBLISHED: 2018-07-23
October CMS version prior to build 437 contains a Cross Site Scripting (XSS) vulnerability in the Media module and create folder functionality that can result in an Authenticated user with media module permission creating arbitrary folder name with XSS content. This attack appear to be exploitable v...
CVE-2018-19990
PUBLISHED: 2018-07-23
October CMS version prior to Build 437 contains a Local File Inclusion vulnerability in modules/system/traits/ViewMaker.php#244 (makeFileContents function) that can result in Sensitive information disclosure and remote code execution. This attack appear to be exploitable remotely if the /backend pat...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit cced03dd667a5df6df8fd40d8de0bff477ee02e8 contains multiple out of array access vulnerabilities in the mms protocol that can result in attackers accessing out of bound data. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fix...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit 2b46ebdbff1d8dec7a3d8ea280a612b91a582869 contains a Buffer Overflow vulnerability in asf_o format demuxer that can result in heap-buffer-overflow that may result in remote code execution. This attack appears to be exploitable via specially crafted ASF file that has to be provide...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit 9807d3976be0e92e4ece3b4b1701be894cd7c2e1 contains a CWE-835: Infinite loop vulnerability in pva format demuxer that can result in a Vulnerability that allows attackers to consume excessive amount of resources like CPU and RAM. This attack appear to be exploitable via specially c...