vulcan-exposed-db check consolidation using Nuclei #486
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.
The goal of this PR is deprecate vulcan-exposed-db check in favour of vulcan-nuclei check by providing custom Nuclei templates.
In fact, vulcan-tenable check already report most of the database service exposures but it requires a 3rd party to run and we've decided to provide an open source replacement for the vulcan-exposed-db check instead.
Check changes:
Templates added: