[PR #1190] fix XFF header parsing #186

Open
opened 2026-02-26 02:31:32 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/kgretzky/evilginx2/pull/1190
Author: @rotarydrone
Created: 8/12/2025
Status: 🔄 Open

Base: masterHead: fix-xff


📝 Commits (1)

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 core/http_proxy.go (+2 -1)

📄 Description

In certain reverse proxy scenarios, such as with Cloudflare, the XFF chain may change through the request flow, leading to unexpected behavior with request authorization handling. The fix is to take only the first IP from the XFF chain.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/kgretzky/evilginx2/pull/1190 **Author:** [@rotarydrone](https://github.com/rotarydrone) **Created:** 8/12/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `fix-xff` --- ### 📝 Commits (1) - [`5131ab0`](https://github.com/kgretzky/evilginx2/commit/5131ab0bf40feb4fc77cd8f014d8f5d6da680084) fix XFF header parsing ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `core/http_proxy.go` (+2 -1) </details> ### 📄 Description In certain reverse proxy scenarios, such as with Cloudflare, the XFF chain may change through the request flow, leading to unexpected behavior with request authorization handling. The fix is to take only the first IP from the XFF chain. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/evilginx2-kgretzky#186
No description provided.