Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Burp Collaborator further protocols

S | Last updated: Dec 06, 2018 08:52AM UTC

Hi Burp Team, The burp collaborator is an awesome tool, I often use other protocols on top of HTTP/S and SMTP/S when testing SSRF and XXE however. Do you plan on supporting FTP/S or other protocols? As a dirty hack, one could do a FTP request on port 80 or 25 in order to see if credentials will be added. When I do a http connection (with curl) on port 25, I get a hit from the collaborator, however when I do a ftp connection on port 25 (with ftp), the collaborator does not report the (failed) SMTP Conversation. Can you look into that? Thanks a lot for your great tool, cheers, S

PortSwigger Agent | Last updated: Dec 06, 2018 09:08AM UTC

Glad you find the Collaborator useful. We don't have any short term plans to implement further protocols. If your target uses an unsupported protocol you will still get a DNS interaction, which is an indication you should manually investigate. The SMTP interaction will trigger if there's an interaction ID in the data received. When you used the FTP client, the ID will not have been sent, although you should still get a DNS interaction.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.