Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change SCAP and CERT data to use new severity scoring #1333

Merged
merged 7 commits into from
Oct 26, 2020

Conversation

timopollmeier
Copy link
Member

@timopollmeier timopollmeier commented Oct 22, 2020

What:
This changes SCAP and CERT data to use the new 0-100 severity scoring system.
CVEs will now also use CVSS-v3 data if available.
The fields for individual CVSS vector components are replaced with a single vector string field.

Why:
This is part of adding CVSS-v3 support.

How:
This was tested by checking the get_info GMP responses for the various subtypes.

Checklist:

CVEs, CPEs, OVAL definitions and CERT advisories now use integer scores
from 0 to 100 instead of CVSS scores.
CVEs now also use CVSS v3 if available and store CVSS vector strings
instead of individual components.
The "severity", "cvss", "max_cvss" elements and filters are replaced
with the new score ones. Only the filter keyword "severity" is kept
for filter and aggregate / chart compatibility.
For simplicity all the new score elements and filter columns should be
named the same.
The functions were still trying to use the old "cvss" field.
Also, the doc comment of cve_cvss_base has been fixed.
The doc comments are updated to refer to the new scoring instead of
CVSS scores and -1 instead of NULL for finished iteration values.
@timopollmeier timopollmeier marked this pull request as ready for review October 22, 2020 11:36
@mattmundell mattmundell merged commit c0d90ed into greenbone:master Oct 26, 2020
@timopollmeier timopollmeier deleted the cves-cvss-v3 branch October 15, 2021 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants