Research Academy
My account Customers About Blog Careers Legal Contact Resellers
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

No API stack nor full parameter value when using Infiltrator with a private Collaborator server

Nicolas | Last updated: Mar 18, 2017 06:28PM UTC

[Tested with Burp Suite Pro 1.7.19] I instrument Jenkins 1.580.2 like that: java -jar ${JENKINS_HOME}/infiltrator.jar --non-interactive --report-parameter-values=true --report-call-stacks=true --target-paths=/path/to/war/ If I use the public Collaborator server, everything is fine. But when I use my own Collaborator server (using a dedicated domain), I _never_ have the call stack or full parameter value (using Scanner or the manual client). Is that a known limitation of private Collaborator servers? Did I miss something when configuring my Collaborator? Notes: - the private Collaborator instance uses a self-signed SSL cert + the SMTPS port isn't reachable - health check is OK, with some warnings - I think that instrumentation is OK, because the same patched app works well with a public Collaborator Thanks in advance!

Burp User | Last updated: Mar 19, 2017 10:39AM UTC