Introduce logic for cvss_v4 severity #400
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Team,
I would like to introduce logic for properly rating severity for vulnerabilities which are estimated using only
CVSS:4.0
. This is a followup to rubysec/ruby-advisory-db#654Currently vulnerabilities which are estimated using only
CVSS:4.0
are using default fallback and are being marked asseverity:unknown
.According to specification docs I think severity did not change between 3.0 and 4.0 standards
I did some refactoring based on code climate suggestions
Here is an example:
Using
bundler-audit:0.9.2
Using
bundler-audit:0.10.0
Let me know if there is anything else I should adjust