# AI use cases for Reburp (forefy/reburp) Repo: [forefy/reburp](https://github.com/forefy/reburp) | Use cases: 4 | Page: https://dedupedai.com/use-cases/forefy-reburp/ reburp is a Burp Suite extension that exposes the Montoya API as a local, unauthenticated REST API with OpenAPI docs and Swagger UI, so scripts and AI agents can drive Burp. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Triage Burp proxy history with an AI agent: https://dedupedai.com/use-cases/forefy-reburp/triage-proxy-history-with-an-agent/ - Replay requests with and without tokens to find access gaps: https://dedupedai.com/use-cases/forefy-reburp/replay-requests-to-test-access-control/ - Scope a target and start a Burp scan over REST: https://dedupedai.com/use-cases/forefy-reburp/scope-a-target-and-start-a-scan/ - Capture and drive the Burp window for a bug report: https://dedupedai.com/use-cases/forefy-reburp/drive-the-burp-window-for-a-bug-report/ ## How to triage Burp proxy history with an AI agent with Reburp Repo: [forefy/reburp](https://github.com/forefy/reburp) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Let an agent read recent proxy traffic over REST and rank the most unusual exchanges first. **Who it is for:** A pentester or bug bounty hunter with a large proxy history who wants help finding the interesting requests before reading them by hand. **The problem:** Proxy history grows fast during a browsing session, and scrolling through it to spot anomalies takes time. **The outcome:** A short, ranked list of proxy exchanges that look most anomalous, which the tester can open in Burp to investigate. ### Steps 1. Download Reburp.jar from the Releases page, then in Burp open Extensions, Installed, Add, set Extension type to Java, select the jar, and click Next. 2. Run `curl -s http://127.0.0.1:9090/api/status` to confirm the extension is up. 3. Run `curl -s "http://127.0.0.1:9090/api/proxy/history?limit=10"` to read the latest proxy entries. 4. Open http://127.0.0.1:9090/docs in a browser to find the ranking route under /api/utils/rank in the spec, then point the agent at it. 5. Ask the agent to review the ranked exchanges and list the ones worth opening in Burp. ### Prompt to paste into your agent ```text Using the reburp API at http://127.0.0.1:9090 (spec at /openapi.json), read the latest proxy history for , rank it by anomaly through /api/utils/rank, and return the top 10 exchanges with method, path, and status. Verify that each returned item matches an entry in /api/proxy/history before reporting it. ``` ### Caveat The API is unauthenticated on localhost, so any local process or open web page that can reach port 9090 can read this history. Risk, credentials: Proxy history contains cookies and tokens from the target, so keep the agent output and any exports within the engagement scope. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/forefy-reburp/triage-proxy-history-with-an-agent/ ## How to replay requests with and without tokens to find access gaps with Reburp Repo: [forefy/reburp](https://github.com/forefy/reburp) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Send a request with and without its auth token and diff the responses to spot broken access control. **Who it is for:** A tester checking whether a web app enforces authorization on an endpoint, such as one that returns another user's data. **The problem:** Checking each endpoint by hand with and without a session token is slow and easy to get wrong. **The outcome:** A diff of the two responses that shows whether the endpoint returns the same data without the token, which points to a possible BOLA or BFLA issue to confirm. ### Steps 1. Load Reburp.jar in Burp as described in the Load into Burp Suite section and confirm the server with `curl -s http://127.0.0.1:9090/api/status`. 2. Open http://127.0.0.1:9090/openapi.json and find the HTTP group routes for sending requests, auth-token injection, and diff. 3. Send the target request once with its token and once without, using the send and diff routes under /api/http/ from the spec. (inferred, check the README) 4. Compare the two responses with the diff route and record any endpoint where the response body is unchanged without the token. 5. Confirm each suspected gap manually in Burp Repeater before reporting it. ### Prompt to paste into your agent ```text Using the reburp API at http://127.0.0.1:9090 with the spec at /openapi.json, send for once with its auth token and once without, then diff the two responses. Return whether the responses match and the status codes for each, and verify the result by checking the raw responses in Burp before calling it a finding. ``` ### Caveat Run this only on applications you are authorized to test, and confirm that route names and parameters in the OpenAPI spec before scripting against them. Risk, credentials: The replay uses real session tokens from the target, so store and remove them after the test. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/forefy-reburp/replay-requests-to-test-access-control/ ## How to scope a target and start a Burp scan over REST with Reburp Repo: [forefy/reburp](https://github.com/forefy/reburp) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Add a host to Burp scope with one call, then start an audit or crawl through the scanner routes. **Who it is for:** A tester on a Burp Suite Professional license who wants a script or agent to set up scope and launch scanning for a new target. **The problem:** Setting scope and starting scans by clicking through Burp for each target is repetitive when many hosts are in play. **The outcome:** The target is in scope, a scan is running, and the tester can pull scanner issues over REST when it finishes. ### Steps 1. Load Reburp.jar in Burp and confirm the server with `curl -s http://127.0.0.1:9090/api/status`. 2. Add the target to scope with `curl -s http://127.0.0.1:9090/api/scope/include -H 'Content-Type: application/json' -d '{"url":"https://example.com"}'`, replacing the URL with your target. (inferred, check the README) 3. Open http://127.0.0.1:9090/docs and use the Scanner group under /api/scanner/ to start an audit or crawl and check task status. (inferred, check the README) 4. Poll the scanner task status until the task finishes, then read the issues from the scanner routes. 5. Review each issue in Burp before reporting it. ### Prompt to paste into your agent ```text Using the reburp API at http://127.0.0.1:9090 (spec at /openapi.json), add to scope, start an audit through the scanner routes, and poll task status until it completes. Return the list of scanner issues with names and severities, and verify that the target is in scope with /api/scope before reporting results. ``` ### Caveat Scanner and collaborator endpoints return HTTP 403 on Community edition, so this workflow needs Burp Suite Professional. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/forefy-reburp/scope-a-target-and-start-a-scan/ ## How to capture and drive the Burp window for a bug report with Reburp Repo: [forefy/reburp](https://github.com/forefy/reburp) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Take screenshots of Burp and switch tabs or click elements over REST to document a finding. **Who it is for:** A tester or extension developer writing a report or reproducing a UI-dependent Burp workflow who wants an agent to show each step. **The problem:** Writing up a Burp workflow with screenshots takes manual steps, and reproducing the same clicks for each report is tedious. **The outcome:** A set of screenshots showing each step, taken and driven through the UI routes, ready to attach to a report. ### Steps 1. Load Reburp.jar in Burp and confirm the server with `curl -s http://127.0.0.1:9090/api/status`. 2. Open http://127.0.0.1:9090/docs and find the UI group under /api/ui/ in the spec. 3. Call the UI routes to list tabs, switch to the tab you need, and take a screenshot of the window or element. (inferred, check the README) 4. Use the click, type, or select routes to reach the dialog or element that shows the issue, then take another screenshot. (inferred, check the README) 5. Save the screenshots with the report and check that each one matches the step it documents. ### Prompt to paste into your agent ```text Using the reburp API at http://127.0.0.1:9090 with the spec at /openapi.json, switch Burp to the tab, click , and take a screenshot of the Burp window at each step. Return the screenshot files with a one-line description of each, and verify each screenshot shows the tab or element named before reporting it. ``` ### Caveat The UI routes act on the live Burp window, so run them only when you can watch the screen, because a click can change project state. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/forefy-reburp/drive-the-burp-window-for-a-bug-report/