Burp is one of the most famous tool used by pentesters, which incorporates a full static code investigation engine to discover vulnerabilities. PortSwigger Security released a new Burp Extension Replicator.
The graphical tool is composed in Java and it was Created PortSwigger Security. Burp use to receive frequent updates and it scanning logic is persistently refreshed time to time to ensure it can detect new vulnerabilities.
Also Read Web Application Penetration Testing Checklist – A Detailed Cheat Sheet
BApp Store
The BApp Store holds the Burp Suite extensions that developed by the users of Burp suite to extend its capabilities. By having Burp suite you can install the tool directly via the BApp Store feature in the Burp Extender tool.
Also, it is available for offline download from here.
Added: Replicatorhttps://t.co/mMRHi7Yo6c
— BApp Store (@BApp_Store) February 9, 2018
New Burp Extension Replicator
Burp suite extension replicator helps developers to reproduce the issue that detected by the pentesters. The replicator file holds the findings in the report.
It includes the logic or macros or the session rules that associated in finding the vulnerability, the Pentester can send the replicator file along with the report and the developer can load the file in Burp and replicate the issues.
Once the issue fixed the replicator reports the vulnerability is now fixed and also it recommends retest if the vulnerability exists.
Issues can have the following status
- Vulnerable – The application is still vulnerable.
- Resolved (tentative) – The vulnerability appears to be resolved. The replicator cannot confirm this with certainty; a retest is required for that.
- Unable to replicate – It wasn’t possible to determine if the application is vulnerable. This may be because credentials are invalid. Some fixes (e.g. removing the whole page) can cause this.
Developer workflow – Burp Extension Replicator
- Load the Replicator file.
- If you want to test a different application instance (perhaps a development instance) edit the Hosts section to point to the instance.
- Click Test all. All the vulnerabilities should get status Vulnerable. If any do not, you need to investigate why. You can use the Start Trace button to generate a trace file that may help the pen tester diagnose the issue.
- Save the file. This is important for confirming fixes later.
- Identify an issue to work on. Consult the pen test report for a full description.
- When the application has been updated, click Test to see if it’s still vulnerable.
You can find the Tested Workflow and download the extension from bappstore.The extension was developed by Paul Johnston and PortSwigger.
