mvp for getting scores and severity of vulnerabilities #653
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.
Purpose: we want to retrieve a measure of severity of the vulnerabilities detected, in order to suppress too noisy alerts.
To do so, we introduce an API call to
for each CVE vulnerability detected, either via pypi or via osv.
When the CVE is not present or not found in the database, we return None.
The layout of the tabular output has been changed accordingly to include two new columns,
score
andseverity
, which are respectivelyThe new output looks like this:
json and cyclonedx output have also been changed so that the severity and score will be visible therein.
Since NVD has a limit of 5 requests over a moving window of 30 seconds, we included the possibility of using an api-key from one's environment, if that is present (as
NVD_API_KEY
). This will increase the limit to 50 requests per 30 seconds, which should cover most use-cases.A disclaimer for using NVD API has been added, for complying with NVD requests when using their product