fix: templates with generic tag should not depend on specific tech #8009
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
|
Hi @adrlsx Thank you for your contribution to this project. Your efforts are greatly appreciated. Cheers! |
pussycat0x
approved these changes
Aug 19, 2023
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.
Generic tag harmonization
Some templates were wrongfully tag generic.
This small PR removes the generic tag from templates depending on a specific technology like AWS or Akamai.
In the same logic, no CVE should be marked as generic.
Generic tags were also added to certain templates, for example those in http/exposures/tokens/generic/.
Reproducibility
Template Validation
I've validated this template locally?