DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to replay requests with and without tokens to find access gaps with Reburp

Send a request with and without its auth token and diff the responses to spot broken access control.

Authorization notice. Reburp is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The replay uses real session tokens from the target, so store and remove them after the test.

Who it is forA tester checking whether a web app enforces authorization on an endpoint, such as one that returns another user's data.

The problemChecking each endpoint by hand with and without a session token is slow and easy to get wrong.

The outcomeA 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.

What you need first

  • Burp Suite with the Montoya API (reburp 1.1.14 lists 2026.7 as minimum; older Burp needs the matching older jar from Releases)
  • The reburp-*.jar from the Releases page, or Java 17+ to build from source
  • Written authorization to test the target systems
  • A terminal with curl, or an AI agent that can make HTTP calls to 127.0.0.1:9090

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 for your agent

Using the reburp API at http://127.0.0.1:9090 with the spec at /openapi.json, send <request description> for <target host> 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page