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
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Hunny, I looked every where for the dorritos. 
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8567
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569
PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, ...
CVE-2020-8570
PUBLISHED: 2021-01-21
Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executi...
CVE-2020-8554
PUBLISHED: 2021-01-21
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typicall...