Burp Carbonator does not work for me
I am trying to play around with the carbonator feature of Burp using the demo.testfire application as a test run and had a few questions and issues.
I have installed carbonator and using the command " java -jar <path to burp> http://demo.testfire.net/bank/login.aspx 80". However, this just opens the Burp instance and does not do anything. Is there anything that I am missing out on?
Does Carbonator do an authenticated scan? If yes, how?
The Cabonator command line is slightly different to what you’ve used. Try this:java -jar path/to/burp.jar http demo.testfire.net 80 /bank/login.aspx
If that doesn’t work, go to Extender > Extensions > Carbonator > Errors – you may get an error message explaining what’s wrong.
For authenticated scans, first configure Spider with credentials and confirm that Spider is logging in correctly. The relevant area is Spider > Options > Application login.
Then click the cog icon next to Application Login, choose Save options and select “auth”.
You can then start Burp like this:java
It may take some experimentation, but you can get authenticated Carbonator scans working this way.
Here is how I attempted it:
Launched Burp, went to spider and entered id/password in Spider->Options->Application Login. Saved them to a file - it did get saved to auth.json. Went to Proxy and turned Intercept to Off.
Adjusted proxy setting in browser and then browsed to the application URL. Got presented with a login screen. I did not enter credentials as I wanted to check that Burp spider is able to login using that I supplied.
Switched back to Burp and in Target->Sitemap saw the application URL show up. I added it to scope. Then right click the application url in Target->Sitemap->Spider this host. Checked in the Spider tab that the spider was not running (has finished). However looking at the url it found in the Sitemap it clearly was unable to get past the login.
Is this supposed to work?
Note: If I login to the application from the browser and launch spider after it then it seems to gather a couple of URLs but then it is just using the session that was established from browser.
What version of Burp are you using. The authentication support in Burp 1 is quite basic and fails on quite a lot of applications. However, this is greatly improved in the Burp 2 beta. If you move to the Burp 2, you’re probably best not using Carbonator and instead using the native REST API to launch a scan.
If Burp 2 fails to login it would be really helpful if you could share the HTML source for the login page.
Where can I find documentation on the REST API and its usage?
Does this issue with authentication Burp 1.x also exist in the Enterprise edition? And/or does the latest version of Enterprise edition have a better authentication support like 2.x Pro beta.
There’s documentation on the REST API if you visit the service with a browser. Look in User options > Misc > REST API and enable the service. If you visit with a browser, there’s an interactive request builder, and you can get an OpenAPI spec.
Burp Enterprise uses Burp 2 internally so it has the improved authentication support.
Please let us know if you need any further assistance.