Report CVEs from the NVD when affected packages have unspecified version #5284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomasTurina
reviewed
Jun 23, 2020
JcabreraC
changed the title
[Vuln-detector] Use package vendor to discard NVD vulnerabilities
TomasTurina
approved these changes
Jun 29, 2020
chemamartinez
approved these changes
Jun 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Currently, by adding the NVD as a feed for Linux agents, vulnerabilities that the NVD includes in affected packages without specifying the version, do not report alerts to avoid false positives.
This PR is to study those vulnerabilities that are marked as undetermined (needs triage, ignored, unfixed) and that the NVD reports the packages as affected without specifying a range of vulnerable versions.
With this change, the number of alerts increases, and we now alert of vulnerabilities that according to the vendor's OVAL are vulnerable and that we did not report before.
Tests