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.

Application Security

5/17/2019
03:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Q1 2019 Smashes Record For Most Reported Vulnerabilities in a Quarter

Once again, a high-proportion of the reported flaws have no current fix, according to Risk Based Security.

More security vulnerabilities were publicly disclosed in the first quarter of this year than in any previous three-month period.

Troublingly, nearly four-in-10 (38.2%) of them currently have no known fixes, according to Risk Based Security, which recently analyzed vulnerability data for the firts quarter of 2019 collected from its own proprietary search engine and from various security vulnerability-reporting sites.

The analysis showed a total of 5,501 vulnerabilities were disclosed via coordinated and uncoordinated disclosures during the first three months of this year. Nearly 38% of the vulnerabilities currently have publicly available exploits.

The total number vulnerabilities in Q1 2019 was about 1% higher than the 5,375 recorded in the same period last year, and is the highest ever in a quarter since Risk Based Security began conducting these studies. Web-related vulnerabilities as usual accounted for most (56.8%) of the reported vulnerabilities last quarter—an almost 10% increase from Q1 of 2018.

"Vulnerability disclosures continue to rise, and will continue to rise every year," says Brian Martin, vice president of vulnerability intelligence at Risk Based Security. The trend highlights the need for organizations to have vulnerability mitigation plans and processes that go beyond just patching, he says.

"With some days seeing hundreds of disclosures, IT simply cannot patch all the vulnerabilities right away," Martin notes. They need to triage that process and prioritize the high-impact vulnerabilities using more than just the risk rating provided by vendors and others. "They need to make more informed decisions based on their own deployment, availability of exploits, and more," he notes.

Product Integrity

Sixty-three percent of the security vulnerabilities disclosed last quarter affected product integrity. Bugs that fall into this category include those that enable data manipulation, SQL injection, and code execution. Over half could be attacked remotely and one-third were user-assisted or context-dependent, meaning the ability for attackers to exploit these flaws depended on user actions and specific context.

Risk Based Security's analysis showed that some 14% of the vulnerabilities that were disclosed last quarter were critical, with severity ratings of 9 or higher on the CVSS scale. Typically, these are bugs that are remotely exploitable, provide unauthenticated access, or give attackers a way to gain root access to a critical system or data. Thirteen percent of the reported flaws last quarter could only be exploited if attackers had local access to a system or a device.

Somewhat ominously for organizations, a higher-than-usual proportion of the vulnerabilities that were disclosed last quarter (38.2%) have no current fixes. In fact, only 60.8%--or 3,275—of the disclosed vulnerabilities have either an updated software version or a patch available. The number of vulnerabilities with available fixes last quarter was some 13.5% lower compared to Q1, 2018.

Martin says many of the vulnerabilities for which there are no fixes were disclosed by security researchers through channels outside the vendor's purview. 

"If they release via an exploit site, their own blog, or anywhere else that a vendor doesn't know to look, they wouldn't be aware of it and know to start working on a fix," Martin says.

In addition to such uncoordinated disclosures, researchers sometimes release vulnerability details publicly if they perceive the vendor as being too slow to issue a fix for it.

Also, there are some security vulnerabilities reported in projects that are abandoned and will not be updated and therefore no fix is available, Martin says.

Related Content:

 

 

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
ToddS207
50%
50%
ToddS207,
User Rank: Apprentice
5/23/2019 | 5:53:01 PM
Question to the editor - Isn't the problem with the vendor and their lack of Q/A?
Microsoft presents software to the public and then they send patches to update it. It seems all of the OEMs are doing the same thing.

So shouldn't there be a financial pentality from GDPR that should be placed on the software manufacturer to address some of these security vulnerabilities/issues.

Todd
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
Video
Cartoon
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
CVE-2020-15208
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 ...
CVE-2020-15209
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....
CVE-2020-15210
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 ...
CVE-2020-15211
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...
CVE-2020-15212
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...