Saturday, February 8, 2025
HomeWebapp PentestingNew Valuable Burp Extension that helps Developers to Reproduce Issues Detected by...

New Valuable Burp Extension that helps Developers to Reproduce Issues Detected by Pentesters

Published on

SIEM as a Service

Follow Us on Google News

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.

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

  1. Load the Replicator file.
  2. If you want to test a different application instance (perhaps a development instance) edit the Hosts section to point to the instance.
  3. 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.
  4. Save the file. This is important for confirming fixes later.
  5. Identify an issue to work on. Consult the pen test report for a full description.
  6. 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.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Hackers Leveraging Image & Video Attachments to Deliver Malware

Cybercriminals are increasingly exploiting image and video files to deliver malware, leveraging advanced techniques...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Web Server Penetration Testing Checklist – 2024

Web server pentesting is performed under three significant categories: identity, analysis, and reporting vulnerabilities such as...

ReconAIzer: OpenAI-based Extension for Burp Suite

Burp Suite, the renowned Bug Bounty Hunting and Web Application Penetration Testing tool, has...

HackerOne Lays off 12% of Its Employees as a One-Time Event 

HackerOne is a renowned cybersecurity company that offers bounty and penetration testing platforms to...