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.

Comments
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Newest First  |  Oldest First  |  Threaded View
Ericka Chickowski
100%
0%
Ericka Chickowski,
User Rank: Moderator
5/16/2018 | 1:04:08 PM
Re: CVE, CVSS, Public Exploits
Thanks, for your input, Michael. I updated the story to clarify CVSS scores of 10 or higher and invited the Kenna Security folks to discuss the issue of percentage of vulns with public exploits.
danmellinger
50%
50%
danmellinger,
User Rank: Apprentice
5/16/2018 | 12:34:13 PM
Re: CVE, CVSS, Public Exploits
Appreciate the comment. The 2% refers to "observed exploitation events" related to those vulnerabilities. It appears that you're referring to "has an exploit published." (additional background can be found in the Data Sources section of the full report)

The report found that 22.4% of all 94,597 CVE's we looked at (1999-2017) have published exploit code. The difference of that percentage from the Risk Based Security report (31.4%) is possibly due to the difference between our timeframe versus looking at vulns in 2017, which is an interesting insight that there is an increased percentage of published exploits in 2017 versus the historical average. In any case both of the reports came to the same conclusion that the majority of vulnerabilities do not have published exploit code. 

For the second part of your comment, it appears that it may be a typo, referring to CVE instead of CVSS, as CVSS is correctly called out further down in that paragraph. 
MichaelM17101
100%
0%
MichaelM17101,
User Rank: Strategist
5/16/2018 | 1:55:10 AM
CVE, CVSS, Public Exploits
Just to correct some facts. It is not true when Kenna and Cyentia report, just 2% of published vulnerabilities have observed exploits in the wild.  If we look a 2017 from January 1st to December 31st there where discovered 21,691 vulnerabilites. Out of them where there Public Exploits avaialble for 6,818 = 31,4% - source: Risk Based Security's VulnDB. 

Also, it is mentioned that: "So a strategy that goes after really bad CVEs of 10 or higher would have a good efficiency rating but is going to have terrible coverage"  CVE is not used to mesusre the criticality. That is CVSS, and CVSS ends as 10. Every CVSS Score between 7 - 10 is considered critical. 

 

 


97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
How a Manufacturing Firm Recovered from a Devastating Ransomware Attack
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/20/2019
Why AI Will Create Far More Jobs Than It Replaces
John DiLullo, CEO, Lastline,  5/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Talk about vendor lock in...
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11816
PUBLISHED: 2019-05-20
Incorrect access control in the WebUI in OPNsense before version 19.1.8, and pfsense before 2.4.4-p3 allows remote authenticated users to escalate privileges to administrator via a specially crafted request.
CVE-2019-10076
PUBLISHED: 2019-05-20
A carefully crafted malicious attachment could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.
CVE-2019-10077
PUBLISHED: 2019-05-20
A carefully crafted InterWiki link could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking.
CVE-2019-10078
PUBLISHED: 2019-05-20
A carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking. Initial reporting indicated ReferredPagesPlugin, but further analysis showed that multiple plugins were vulnerable.
CVE-2019-12239
PUBLISHED: 2019-05-20
The WP Booking System plugin 1.5.1 for WordPress has no CSRF protection, which allows attackers to reach certain SQL injection issues that require administrative access.