Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 38 ยท Repeater and Intruder

Burp Repeater Basics

Learn Burp Repeater: send a request from history, change one value at a time, read responses, use tabs and groups, and run a safe access-control check in your own lab.

If you only learn one Burp tool well, make it Repeater. It takes a single request, lets you edit anything in it, sends it to the server and shows you the response, as many times as you want, without touching the browser. It is the workbench where hypotheses become evidence.

A manual experiment loop is simple: change one thing, send, read the response, and decide what to try next. Repeater makes that loop take seconds, and keeps every attempt visible so you can compare them.

Sending a request to Repeater

From almost anywhere in Burp (HTTP history, site map, an intercepted request) right-click the request and choose Send to Repeater, or press Ctrl+R (Cmd+R on macOS). A new numbered tab appears. You can rename tabs by double-clicking, which is worth doing: "orders-id-test" is more useful than "14".

The Repeater layout

TEXT
[Send] [Cancel] [<] [>]   Target: https://shop.lab.test      [Follow redirection]
-------------------------------------------------------------------------------
Request                              |  Response
Pretty | Raw | Hex                   |  Pretty | Raw | Hex | Render
GET /api/v1/orders/1001 HTTP/2       |  HTTP/2 200 OK
Host: shop.lab.test                  |  Content-Type: application/json
Cookie: session=abc123               |
Accept: application/json             |  {"id":1001,"owner":"alice","total":42.5}

A text mock-up of the real window. Request on the left, response on the right, Inspector panel at the side.

Key controls:

  • Send: transmit the request as edited. Cancel stops a slow one.
  • < and >: step back and forward through your history of edits in this tab, so you can return to a request you changed.
  • Target: the host and port the request goes to (not necessarily the same as the Host header; you can change one without the other).
  • Follow redirection: automatically follow a 302 to see where it leads.
  • Inspector (right panel): structured editing of query parameters, body parameters, cookies and headers; Burp keeps encoding and Content-Length correct.
  • Search bar under each pane: find text, with regular expression support.
  • Render: shows the response as a page, which is handy for HTML but should be used cautiously (it can load external resources).

A worked experiment (your own lab)

You are testing whether one user can read another's order. You have two lab accounts, alice (order 1001) and bob (order 1002).

  1. Log in as alice in the browser and open her order. Send the request GET /api/v1/orders/1001 to Repeater.
  2. Click Send. Response: 200 with her order.
  3. Change only the path to /api/v1/orders/1002 (Bob's order) and Send.
  4. Read the result.
    • 403/404: the server checks ownership. Good.
    • 200 with Bob's data: broken access control (an insecure direct object reference). Confirm with one record, stop, and write it up.

Then test related ideas, one at a time: remove the cookie (expect 401), change GET to DELETE, add a header such as X-HTTP-Method-Override.

Good Repeater habits

  • One change per send. If you change three things and the result differs, you will not know why.
  • Keep a baseline. Leave one tab with the original working request, and clone it (right-click > Duplicate tab) before experiments.
  • Name tabs and use tab groups to organise by feature; colour them.
  • Watch for state. Some requests are not repeatable: single-use tokens, CSRF values, expiring sessions. Refresh the token from a fresh response.
  • Compare responses. Use the word-length and status columns, or send two responses to Comparer.
  • Be careful with destructive requests. DELETE /orders/1002 really deletes it. In a lab, fine; in an engagement, only on test data.

Sending several requests together

Repeater can send a group of tabs sequentially or in parallel. Parallel sending (including an optimised "single-packet" mode over HTTP/2) is used to test race conditions, such as applying a one-use coupon twice at the same moment. This is a powerful technique that needs permission and care: it generates simultaneous state changes.

HTTP/2 and other protocols

For HTTP/2 targets, Repeater shows a readable form and the Inspector lets you edit pseudo-headers. You can switch the protocol the request uses in the Inspector (Request attributes). Burp also handles WebSocket messages in a dedicated Repeater view.

Try it: a Repeater stand-in against a fake app

This stand-in gives you a pretend API as a Python function and a send helper, so you can run the access-control experiment above without touching any real system.

Python Stand-in: a Repeater loop against a fake API

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Alice reading Bob's order and getting 200 is the vulnerability: the lab app authenticates but never authorises. The fix is a server-side ownership check.

Try it: fix the app and retest

A second stand-in applies the fix and re-runs the same requests, the way you would retest after a developer says "fixed".

Python Stand-in: retest after the fix

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Note the fix returns the same 404 for "not yours" and "does not exist", so an attacker cannot learn which order numbers are real.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why change only one thing per send in Repeater?

    Isolating variables keeps the experiment interpretable and makes findings reproducible.
  2. 2. In the order experiment, what does a 200 response with Bob's data to Alice's session show?

    The server authenticated Alice but did not check she owns order 1002.
  3. 3. What is Repeater's Ctrl+R shortcut used for?

    Ctrl+R (Cmd+R on macOS) sends the selected request to a new Repeater tab.
  4. 4. What kind of testing uses parallel sending of grouped tabs?

    Sending requests at the same instant can reveal flaws where checks and updates are not atomic. It needs permission and care.

Summary

  • Repeater is the manual workbench: edit one request, send, read, repeat.
  • Send items to it with a right-click or Ctrl+R; name and group tabs; keep a baseline.
  • Change one thing at a time; refresh single-use tokens.
  • The order-id experiment shows a classic access-control test, and how a fix should answer.
  • Parallel group sending tests race conditions; use it only with permission.

Next: Decoder and Comparer