Xref check arguments #714
Merged
Xref check arguments #714
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
Kraemii
force-pushed
the
xref-check-arguments
branch
from
3399556
to
a95a6d1
Compare
jjnicola
approved these changes
Apr 27, 2021
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.
What:
Fixed NASL-linter to catch Syntax error when wrong Arguments were used with script_xref
example:
script_xref(name: "URL", valie: "[https://www.wordfence.com/blog/2017/10/zero-day-vulnerability-ultimate-form-builder-lite/"
gave no error message for wrong spelling of value
Why:
Linter was not able to catch a Syntax Error, but the scanner itself does
How:
I tested the case described in the Issue so that a error message is now shown if one of the parameters is missing or misspelled. No error message is shown if everything is correct.
Checklist: