Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
CVSS is a score from 0 to 10 for the severity of a vulnerability. IPA explains that it is a common evaluation method that does not depend on any vendor, so severity can be compared on the same basis. When an advisory shows a number such as "CVSS 9.8", this is the score it means.
How does CVSS work?
It resembles the figures on a health check. Blood pressure and blood sugar are measured on a fixed scale, so different people can be lined up and compared. But as with a medical report, the number alone does not settle what to do next.
The score is built by combining evaluation criteria. IPA's material, which explains CVSS v2, names three: base, temporal, and environmental. The base criteria measure the nature of the vulnerability itself. They look at whether it can be attacked from the network and how far it leads to leaked or rewritten information or to a stoppage, and they do not change over time.
The temporal criteria reflect the situation now, such as whether attack code is circulating and whether countermeasure information exists. The environmental criteria also take in the user's own setting and the size of secondary damage, so the value differs from one user to the next.
Version 4.0, the current one, is arranged a little differently. The FIRST specification divides it into four groups: base, threat, environmental, and supplemental. The threat criteria measure the current situation, such as the attack technique and how easily the code can be obtained, and play a role close to v2's temporal criteria.
Advisories usually show the score from the base criteria. The FIRST specification for version 4.0 sets the bands as 0.1 to 3.9 Low, 4.0 to 6.9 Medium, 7.0 to 8.9 High, and 9.0 to 10.0 Critical. In our own explanations, 9 and above is called urgent and 7 and above serious.
Why does CVSS matter?
It gives you a basis for deciding the order of updates. New holes are announced almost every month, and treating all of them as equally heavy leaves no time for the work. If you look at the high scores first, you can put limited time into the work with the biggest effect.
The FIRST specification is also careful to say that CVSS expresses severity from technical characteristics. Regulatory requirements, the number of customers affected, and financial loss fall outside CVSS.
A site with a checkout screen that handles card data and a site with only a company profile should not hurry equally, even at the same score. Lay your own circumstances over the score when you decide.
What should you do with a score?
- Find the CVE number and the affected versions in the advisory, and compare them with what you run.
- Note the score, and note which CVSS version it came from.
- If your product is affected, decide the order: high scores and confirmed attacks first.
- Add your own context, such as card data or personal information on the affected screen.
If you are unsure how to read a score or in what order to fix things, contact us.
Related terms
- Vulnerability: the security hole to which a score is given
- CVE: the worldwide number that identifies that hole
Frequently asked questions
If a CVSS score is 9.0 or higher, should I update at once?
It is a signal to hurry, but do not decide on the score alone. CVSS shows technical severity and does not express how large the damage would be for your own business. Judge it together with whether the product you use is affected and whether attacks have already been confirmed.
Can I leave a low-scoring vulnerability alone?
We do not recommend it. Even a low score can be used in combination with other holes. Putting it later in the queue is fine, but keep an update on the schedule.
Why does the same vulnerability have different scores in different documents?
CVSS has versions, and the detailed scoring rules differ between them. For example, JVN#43511918 records a CVSS v3 base score of 4.7 and a CVSS v4.0 base score of 5.3. Check which version a score belongs to before you compare.
Next step
For help deciding which holes to fix first, contact us and tell us your situation. The free URL check shows only what is visible from outside. The basic terms are in vulnerability.
Frequently asked questions
If a CVSS score is 9.0 or higher, should I update at once?
It is a signal to hurry, but do not decide on the score alone. CVSS shows technical severity and does not express how large the damage would be for your own business. Judge it together with whether the product you use is affected and whether attacks have already been confirmed.
Can I leave a low-scoring vulnerability alone?
We do not recommend it. Even a low score can be used in combination with other holes. Putting it later in the queue is fine, but keep an update on the schedule.
Why does the same vulnerability have different scores in different documents?
CVSS has versions, and the detailed scoring rules differ between them. For example, JVN#43511918 records a CVSS v3 base score of 4.7 and a CVSS v4.0 base score of 5.3. Check which version a score belongs to before you compare.