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.

Vulnerabilities / Threats

8/27/2020
04:15 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Vulnerability Volume Poised to Overwhelm Infosec Teams

The collision of Microsoft and Oracle patches on the same day has contributed to risk and stress for organizations.

Vulnerability disclosures for 2020 are on track to meet or surpass the number disclosed in 2019, researchers report, and the timing of these bug disclosures could prove risky and stressful for security teams.

Risk Based Security's VulnDB team aggregated 11,121 vulnerabilities during the first half of this year, researchers state in its "2020 Mid Year Vulnerability QuickView Report." The first quarter of 2020 saw a decline in quantity and an increase in severity of flaws disclosed. Trends indicate the numbers are returning to normal, albeit with a few significant factors quickly driving them up.

One of these is the occurrence of disclosures by Microsoft and Oracle on the same day. These events have been responsible for 818 flaw disclosures, or 7.3% of the total count for 2020. Researchers call them "Vulnerability Fujiwhara," and they are rare. Two occurred in 2015; the next two will occur in 2025, a conclusion made based on predictable patch releases by the biggest vendors. 

This year brought three of them: January 14, April 14, and July 14. 

Related Content:

6 Signs Your Supply Chain Risk Just Shot Up

Average Cost of a Data Breach in 2020: $3.86M

"The trend over the past year or two is that more vulnerabilities are being disclosed on Patch Tuesday than any other day of the month," says Brian Martin, vice president of vulnerability intelligence at Risk Based Security. "It's very much an outstanding year as far as the pattern goes."

While Patch Tuesday started with Microsoft, other companies soon followed. Adobe began releasing patches on the same day in 2012; since then, SAP, Siemens, and Schneider Electric have joined. Sometimes other vendors, such as Apple, Mozilla, Intel, and Cisco, will release fixes on the same day. On April 14, 506 new vulnerabilities were reported, 79% of which came from seven vendors. July 14 saw 491 disclosures, with 67% from Microsoft and Oracle alone.

"Five hundred vulnerabilities in one day is absolutely brutal for any organization that runs all three of those platforms and software systems in their organization," Martin says of Microsoft, Oracle, and Adobe. 

The number of Microsoft vulnerabilities disclosed increased by 150% compared with last year, researchers note in the report. There could be several factors for the spike, Martin notes. Microsoft has become more receptive of bug reports and engaged with the researcher community. Its Windows 10 codebase is larger than Windows 7, creating more room for underlying flaws.   

Oracle is next highest with 612 disclosed, followed by Google (563), Red Hat (550), SUSE (519), IBM (446), Dell (430), Cisco (376), Canonical (363), and Software in the Public Interest (293). 

Products with the most bugs include Windows 10 (478), openSUSE Leap (464), Windows Server 2019 (436), Windows Server Semi-Annual Channel (425), Windows Server 2016 (366), Ubuntu (362), Red Hat Enterprise Linux (353), Google Pixel/Nexus Devices (314), and Debian Linux (292). Martin notes that Linux environments may have an easier patching time than Windows shops: Windows 10 organizations had consistently fewer, but much higher, disclosure days. Those using OpenSUSE Leap saw few spikes in a large number of disclosures, forcing admins to be more proactive about frequent patching. 

The increase of vulnerability disclosures makes things difficult for security teams, which will undoubtedly find themselves overwhelmed when Patch Tuesday hits. Microsoft does a lot of testing, Martin notes, but it can't test for every configuration or possibility. As a result, firms will need to conduct the patch testing themselves.

"It could be days or weeks before they're given the green light to start to install the patches on the production network," he says. "All contribute to a growing window of vulnerability."

Teams are under pressure to triage, test, and deploy patches in as little time as possible, knowing the bad guys are also racing to write an exploit. With the increase in bugs to address, what once took hours now could take a full day.

In the first quarter of 2020, the number of vulnerabilities disclosed had considerably declined. The instinct is to blame COVID-19, Martin says, but it's impossible to say whether that's entirely the case. Many businesses cut budgets and staffing toward the beginning of the pandemic. It's possible they prioritized fixing bugs over disclosing them. As a result, advisories aren't shared.

Another factor driving the shift is where researchers disclose. Twenty years ago, every flaw went through a couple of mailing lists or website. Now researchers are challenged to track the many blogs, GitHub repositories, and other sources where new flaws are shared. 

Over time, Martin expects numbers will continue to increase as more sources are discovered. By the third quarter and year's end, he believes the count will return to normal – if not higher.

"There's a lot of motivation to find vulnerabilities, and you always want to find them either in products that have a very high deployment or high visibility and profile," he adds.

Windows is a perfect example for broad usage and SCADA for high profile. While most organizations don't use SCADA systems themselves, everyone relies on them.

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
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.