Capture credentials in multipart/form-data
#1152
Open
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.
This PR adds support to :
type: 'post/multipart'
incredentials
section)type: 'post/multipart'
inforce_post
section)Capture creds:
Phishlet section:
Request:
Evilginx:
NB: As said above, incoming phishing URLs will be converted to original/legitimate ones similarly to what is done for regular POST requests (
application/x-www-form-urlencoded
). Files (if any) are also proxied. The resultingContent-Length
is computed by creating a new multipart body (with the same boundary).Force parameters:
Phishlet section:
Incoming request (sent by the browser to Evilginx through Burp):
Outgoing request (sent by Evilginx to the original site through Burp):
NB: Parameter names for files can be used as search
key
but thevalue
will be ignored.