My Software has a Vulnerability, should I worry?
Luca Allodi, Fabio Massacci

TL;DR
This study critically evaluates the effectiveness of CVSS scores in predicting real-world exploitation of software vulnerabilities, revealing limited risk reduction from high scores and highlighting the need for better risk metrics.
Contribution
It provides an empirical comparison of vulnerability datasets and assesses the reliability of CVSS scores as risk indicators for actual exploitation.
Findings
High CVSS scores yield negligible risk reduction.
Proof of concept exploits offer limited additional risk mitigation.
Black market presence correlates with similar risk reduction as wearing a seatbelt.
Abstract
(U.S) Rule-based policies to mitigate software risk suggest to use the CVSS score to measure the individual vulnerability risk and act accordingly: an HIGH CVSS score according to the NVD (National (U.S.) Vulnerability Database) is therefore translated into a "Yes". A key issue is whether such rule is economically sensible, in particular if reported vulnerabilities have been actually exploited in the wild, and whether the risk score do actually match the risk of actual exploitation. We compare the NVD dataset with two additional datasets, the EDB for the white market of vulnerabilities (such as those present in Metasploit), and the EKITS for the exploits traded in the black market. We benchmark them against Symantec's threat explorer dataset (SYM) of actual exploit in the wild. We analyze the whole spectrum of CVSS submetrics and use these characteristics to perform a case-controlled…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsInformation and Cyber Security · Cybercrime and Law Enforcement Studies · Suicide and Self-Harm Studies
