Allow feature specific whitelists #188
Open
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
This change allows specific CVEs to be whitelisted when they affect a specific feature. This is useful when a feature embeds a vulnerable component, but uses it in a way that is not affected by the vulnerability - and the user wants to ensure the CVE does not affect other features (such as the OS Distribution's own package that distributes the component). See https://security-tracker.debian.org/tracker/CVE-2019-8457 for a motivating example. Users may want to whitelist CVE-2019-8457 in the context of the db5.3 package, but still be confident that sqlite3 has been patched.
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.
This change allows specific CVEs to be whitelisted when they affect a
specific feature. This is useful when a feature embeds a vulnerable
component, but uses it in a way that is not affected by the
vulnerability - and the user wants to ensure the CVE does not affect
other features (such as the OS Distribution's own package that
distributes the component).
See https://security-tracker.debian.org/tracker/CVE-2019-8457 for a
motivating example. Users may want to whitelist CVE-2019-8457 in the
context of the db5.3 package, but still be confident that sqlite3 has
been patched.