feat(debian): emit fixed ins for version 0 records#1137
Open
willmurphyscode wants to merge 1 commit intoanchore:mainfrom
Open
feat(debian): emit fixed ins for version 0 records#1137willmurphyscode wants to merge 1 commit intoanchore:mainfrom
willmurphyscode wants to merge 1 commit intoanchore:mainfrom
Conversation
Previously, the Debian provider would drop records where upstream data indicated a package was fixed at "version 0", since these records could never result in a vulnerability match in grype. However, this left downstream providers unable to distinguish between a "search miss" (upstream data has no mention of this CVE/package/distro version tuple) and an explicit indication of "not affected" (Debian maintainers believe this CVE/package/distro version tuple is not affected). Instead, forward the idea of "fixed at version 0" into the results, so that downstream consumers can distinguish between a search miss and a package that maintainers believe is not affected. Signed-off-by: Will Murphy <willmurphyscode@users.noreply.github.com>
8 tasks
This file contains hidden or 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
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.
Previously, the Debian provider would drop records where upstream data indicated a package was fixed at "version 0", since these records could never result in a vulnerability match in grype. However, this left downstream providers unable to distinguish between a "search miss" (upstream data has no mention of this CVE/package/distro version tuple) and an explicit indication of "not affected" (Debian maintainers believe this CVE/package/distro version tuple is not affected).
Instead, forward the idea of "fixed at version 0" into the results, so that downstream consumers can distinguish between a search miss and a package that maintainers believe is not affected.