The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

A flag to Prevent polling collaborator through socks 5 proxy

Breno | Last updated: May 16, 2023 10:28PM UTC

Sometimes, there is a need to set up a SOCKS proxy to an internal host. However, in certain network proxy settings, Oastify and custom collaborator servers may be blocked. In such cases, it would be ideal to have a flag that allows for using the proxy for all HTTP connections while still being able to poll the collaborator using my own network. This flag would address this particular issue and cater to this specific use case.

Michelle, PortSwigger Agent | Last updated: May 17, 2023 01:45PM UTC

Thanks for your message. Can you tell us more about your setup in this use case? Can the application you are testing see the public Collaborator server, but the machine where you have Burp installed (when using the SOCKS proxy) cannot see the public Collaborator server? How often do you come across this scenario?

Breno | Last updated: May 17, 2023 10:49PM UTC

> Can the application you are testing see the public Collaborator server, but the machine where you have Burp installed (when using the SOCKS proxy) cannot see the public Collaborator server? > but the machine where you have Burp installed can see the public or my custom collaborator socks5 can't see public or my custom collaborator My target can see public collaborator server to address this issue i'm using interactsh cli to test my targets ( outside burp and without socks5 ofcourse haha) but would be better if we had a option to poll results inside burp suite bypassing socks5 configuration. > How often do you come across this scenario? i do internal penetration tests so everyweek? hahaha

Michelle, PortSwigger Agent | Last updated: May 18, 2023 03:55PM UTC