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

04:15 PM
Connect Directly

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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...