added ability to force JSON parameters as boolean#1164
Open
callightmn wants to merge 2 commits into
Open
Conversation
|
Hi, could you also open a pull request to our fork at https://github.com/CSIRT-MU/evilginx2? I’m not sure if the maintainer is actively updating this version. |
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
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,
Currently, Evilginx only force posts JSON parameter values as string but it may happen that the server expects values of a certain type only (boolean in my case). I added an optional
typeparameter in theforcesection offorce_postto be able to later cast the injected value inSetJSONVariable.For now, only booleans and strings (which is the default not to break backward compatibility) are supported but integers may be a good addition for instance. The code should be relatively simple to patch to add new types:
SetJSONVariableand call the adequate method from strconv*op_f.TypePhishlet snippet:
Current and default behavior (without
typeortype: "string") - modified request (from Evilginx to remote site):Expected behavior (with snippet above) - modified request (from Evilginx to remote site):