Add high_consequence flag to template #65
Conversation
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
This commit introduces the high_consequence flag. This is intended for vendors doing analysis to suggest that readers focus on a particular vulnerability as it may be more exploitable or more consequential than other vulnerabilities. This does not increment the template version, as it adds a field without modifying existing fields.
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 commit introduces the high_consequence flag. This is intended for vendors doing analysis to suggest that readers focus on a particular vulnerability as it may be more exploitable or more consequential than other vulnerabilities.
This does not increment the template version, as it adds a field without modifying existing fields.
As discussed in our cloud-lts meeting on 2-Oct.