[Teamserver-Client--Bug]: Teamserver ignores "X-Forwarded-For" header

Contact Details

greyhatfeedback@protonmail.com

What happened?

When using redirectors with Havoc C2, it became necessary to see the IP address of the connection initializer rather than the IP address of the redirector the beacon came from.

The redirectors were configured to pass all the headers along with the HTTP packet

In the havoc profile settings, the TrustXForwardedFor variable was set to true.

Teamserver ignores the X-Forwarded-For header and displays the redirector IP address, although when a packet is normally sent to my C2 server, the X-Forwarded-For header is present

When I send curl myredirector:80 and turn on C2 listening, a packet like this arrives, which has all the necessary headers. But Havoc ignores them.

To redirect the packet I use nginx as a proxy

Did You Do a Pull First?

Latest (You performed a pull first)

Did You Try With the Dev Branch?

Yes (You tried using the dev branch but the problem persist)

Relevant log output

No response

Did You Read Over Your Issue First?

[X] I declare I made an effort and provided the necessary information for replication of the issue.

HavocFramework / Havoc