Make asterisk work with --csrf-token option#4305
Merged
Merged
Conversation
Member
|
@tree-chtsec thx |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
--csrf-tokenoption works well if specify parameter through-p csrfexplicitly.For some user, who didn't trace code that deep, may encounter that
[CRITICAL] anti-CSRF token parameter 'csrf-token' not found in provided GET, POST, Cookie or header values, when using asterisk in commands or request files without-p. For example,--data "id=1*&csrf=xxx"This commit solves the problem mentioned above, make
--csrf-tokenmore general in sqlmap.