mirror of
https://github.com/kgretzky/evilginx2.git
synced 2026-04-25 00:36:10 +03:00
[PR #1134] request / response interception with request / response header capture (new direction attribute in intercept and auth_tokens:http) #171
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/evilginx2-kgretzky#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/kgretzky/evilginx2/pull/1134
Author: @callightmn
Created: 10/24/2024
Status: 🔄 Open
Base:
master← Head:master📝 Commits (3)
b242e22fixed: request interception and http token capture8c5dc25fixed: capture token in request82b09acfeature: ability to intercept response and capture response header📊 Changes
2 files changed (+62 additions, -25 deletions)
View changed files
📝
core/http_proxy.go(+28 -5)📝
core/phishlet.go(+34 -20)📄 Description
Update (23/08/25): the PR adds
Hello there,
This PR contains two quick fixes regarding request interception and HTTP token capture.
Request interception:
Likely a regression introduced by
github.com/kgretzky/evilginx2@e3bef9433c, as the value ofreq.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).🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.