fix: dropping generation of excessively loose cpes #1067
Closed
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
Signed-off-by: cpendery <[email protected]>
|
Thanks Chapman! I'm currently seeing 5,774 unique instances where product and vendor are identical for a CPE from the NVD CPE match dateset though |
Resolved offline, I didn't realize the cpe dictionary wasn't cumulative. PR isn't a fix for the issue |
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
A cpe where vendor and product are identical has never occurred in any data source Grype or Syft uses and it's not in the 2.3 cpe database from NVD. It can lead to false matching, so this PR removes it from being generated
Closes anchore/grype#800 and closes #1066