fixed: request interception and http token capture #1134
+6
−4
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
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.
Hello there,
This PR contains two quick fixes regarding request interception and HTTP token capture.
Request interception:
Likely a regression introduced by e3bef94, as the value of
req.Hostdoes not contain the phishing hostname anymore at the new location but holds the legitimate one. As a result, the comparison fails and the request is not intercepted.HTTP token capture:
The header is indeed captured in the request (e,g,.
Authorizationheader). I just added the check on the domain and path specified in the phishlet (v.domainandv.path).