fix: extract lure params before generating final phish url #5
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,
When sending a campaign, the generation of the phishing URL by Gophish embeds the obfuscated version of the lure parameters added by Evilginx instead of the deobfuscated version. Gophish indeed doesn't extract query parameters before obfuscating the phishing URL, resulting in a nested obfuscation, making lure parameters unusable.
Steps to reproduce:
First email sent without the fix:
As we can see, the
pubkeyparameter added by Evilginx is obfuscated twice in the final URL. As such, it is unusable in redirectors orjs_injectwhen hitting the landing page.Second mail sent with the fix: