logoalt Hacker News

dns_snek • today at 3:19 PM • 1 reply • view on HN

> But risk or severity is not what CVSS measures

Risk is not what the CVSS score measures, correct. However the CVSS base score is first and foremost a measure of severity (of the vulnerability). I think they were being loose with their terminology when they wrote "severity is low" and probably meant to say "risk".

The spec talks about this in depth. Paraphrasing: The base score captures intrinsic characteristics of the vulnerability assuming a (reasonable) worst-case configuration.

It's a measure of "How screwed am I if I'm using this software in this specific-but-reasonable manner?", it's not a measure of "How screwed is everyone using this software?".

P.S. I broadly agree, just adding a minor correction on the terminology.


Replies

da_chicken • today at 3:56 PM

Exactly, yes.

And CVSS v4 does add criteria that let's the provider specify how urgent it is, if it can be automated, etc.

I think the bigger problem is that the scoring system lets you specify a small number of factors and still reach a 10.0, and all the optional and supplemental factors reduce it. Like if you try to enter this vulnerability into v4 and fill out more factors, you easily drop it into the 8s.

So essentially everyone submitting the vulnerability is doing the bare minimum, contributing to the perception that the scores are inflated.

And then people don't use the current version of the score. CVSS 3.1 came out in 2021. CVSS 4.0 came out in 2023. Why the hell is everyone still using 3.1?