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
30% of Q4 Malware was New or Zero-Day
Newest First  |  Oldest First  |  Threaded View
HardenStance
50%
50%
HardenStance,
 User Rank: Strategist
3/31/2017 | 4:31:33 PM
New ?
I'm not about to dispute that traditional AV misses a good amount of malware.

The proposition that a "30%" failure rate is a realiable benchmark for a universal catch-all benchmark for "traditional AV" - whatever that is nowadays - sounds pretty high to me.

And that "30%" is "new"? "Zero-day" ?

Presumably that 30% includes stuff with the tiniest of code deviations from a long established malware family? Is that really 'new' ?

There's certainly the core of a decent case here. I'm good with that.

Seems to me there's a bit of 'amplification' going on as well, though.

 

 

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
3/31/2017 | 3:15:42 PM
Level 3's Chris Richter's take.
I recently chitchatted with Level 3's SVP of Global Security Services, Chris Richter, about this very issue in the enterprise cloud context.

He very readily noted that "From a cloud service provider perspective, the one thing they really need to be wary of, and very cognizant of, is that most of the breaches that occurred last year -- the big, big breaches -- did not involve malware at all. They didn't involve any fancy cutting-edge brilliantly written malicious code. It was all mostly zero-day vulnerabilities that the perpetrators were able to take advantage of. In these virtualized cloud environments, that still remains a huge risk, and the cloud operators need to stay ahead. They need to stay ahead of vulnerabilities and they need to have a Plan B should a zero-day attack happen."

He went on to point out the brisk business that zero-day vulnerabilities have on the black market and gray market -- and that many of the WikiLeaks vulnerabilties had already been long-known to the hacker community.


Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16632
PUBLISHED: 2021-05-15
A XSS Vulnerability in /uploads/dede/action_search.php in DedeCMS V5.7 SP2 allows an authenticated user to execute remote arbitrary code via the keyword parameter.
CVE-2021-32073
PUBLISHED: 2021-05-15
DedeCMS V5.7 SP2 contains a CSRF vulnerability that allows a remote attacker to send a malicious request to to the web manager allowing remote code execution.
CVE-2021-33033
PUBLISHED: 2021-05-14
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
CVE-2021-33034
PUBLISHED: 2021-05-14
In the Linux kernel before 5.12.4, net/bluetooth/hci_event.c has a use-after-free when destroying an hci_chan, aka CID-5c4c8c954409. This leads to writing an arbitrary value.
CVE-2019-25044
PUBLISHED: 2021-05-14
The block subsystem in the Linux kernel before 5.2 has a use-after-free that can lead to arbitrary code execution in the kernel context and privilege escalation, aka CID-c3e2219216c9. This is related to blk_mq_free_rqs and blk_cleanup_queue.