Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 53 ยท Web Application Security

Burp Suite Workflow

Learn how a web testing proxy such as Burp Suite fits an authorized assessment: proxy setup, CA certificate, Repeater, Intruder, Sequencer, Decoder, scanner and extensions, with safe stand-ins.

Browsers hide HTTP from you: they build requests, send them and show a rendered page. Web testing begins by looking at what is really sent. An intercepting proxy sits between your browser and the application so you can see, pause, change and replay every request. Burp Suite is the most widely used commercial example, and similar tools exist (including free, open-source ones). This lesson explains the workflow and what each part is for; the ideas apply to any proxy.

A proxy lets you send arbitrary requests to a server, so use it only on applications you own or are authorized in writing to test. Automated tools such as the scanner and Intruder can send thousands of requests and change data. In this course, practice on your own lab applications. The examples here are descriptive or run against a fake handler in memory.

The idea

Every web flaw in the OWASP lists (injection, broken access control, authentication problems) is exploited by changing what the browser sends: a parameter, a cookie, a header, a hidden field. A proxy gives you control over that. The basic loop is: observe the normal traffic, understand how the application works, modify one thing at a time, compare the response. Tools speed up each step, but the understanding stays with you.

flowchart LR
  A["Browser"] --> B["Intercepting proxy<br/>127.0.0.1:8080"]
  B --> C["Web application<br/>(your lab)"]
  C --> B
  B --> A
  B --> D["History, Repeater, Intruder,<br/>scanner, extensions"]

The proxy sees both directions and keeps a history you can search and replay.

Setting up the proxy

  1. Start the proxy listening on a local address and port (commonly 127.0.0.1 and a port such as 8080; avoid a clash with your web server, and see the port notes in your tool).
  2. Configure the browser (or a dedicated testing browser profile) to use that address as its HTTP proxy. A separate browser profile keeps your daily browsing out of the history.
  3. Install the proxy's CA certificate in that browser. HTTPS traffic is encrypted end to end, so the proxy has to terminate the connection, present its own certificate and open a second connection to the server. If the browser trusts the proxy's certificate authority, this works without warnings.
  4. Define the target scope so the tool only records and attacks your lab host.

That CA certificate is powerful: anyone holding its private key could impersonate sites to that browser. Use it only in a throwaway testing profile or VM, and remove it when the engagement ends. This is also exactly why companies must protect devices that trust corporate proxies, and why certificate pinning exists in mobile apps (see mobile app security).

The main tools

  • Proxy and HTTP history. Intercept toggles let you pause a request, edit it and forward it. History records everything for later search by host, status, parameter or text.
  • Repeater. Send any request again, edit one value and watch the response. It is the workhorse: testing an access control means changing a user ID and comparing; testing an input means changing a parameter and reading the error.
  • Intruder. Automates many variations of one request by marking positions and supplying a payload list: user IDs 1 to 500, a list of passwords for a lockout test, a list of file names. It is rate-sensitive and can cause damage, so limit its speed and scope.
  • Sequencer. Analyzes how random session tokens or reset tokens are. Predictable tokens are a serious flaw.
  • Decoder. Converts between encodings: URL, Base64, HTML entities, hex. Useful for understanding a cookie or parameter before you change it.
  • Comparer. Highlights the differences between two responses, ideal for "did changing this value do anything?"
  • Scanner. Passive scanning looks at traffic you generate and flags problems such as missing headers. Active scanning sends test requests; it is noisy and must be in scope.
  • Extensions. Add features: authorization testing helpers, JSON editors, additional scanners.

A repeater stand-in

The stand-in below defines a fake application handler that has a classic access control flaw: it returns an invoice for any numeric ID without checking the owner. You act as Repeater: send one request as Alice, change the ID, compare.

Node.js Repeater: change one value and compare

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 node:readline or process.stdin), it gets the next line from this box.

In a real assessment you would send the original request from history to Repeater, change id, and see the other user's data. The proof is the response that should not exist. The write-up then says: the fix is an ownership check on the server (see web security basics).

An Intruder stand-in with a safe limit

Intruder runs one request many times with different payloads. The stand-in below enumerates invoice IDs against the vulnerable handler to show how a tester would measure the size of a flaw, with a built-in request cap and a pause setting, because good testers cap their automation.

Node.js Intruder-style enumeration with a cap

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 node:readline or process.stdin), it gets the next line from this box.

Notice what the analysis looks at: a distribution of statuses and response lengths. In real tools you sort the results table by length or status to spot the outlier.

A sensible workflow

  1. Map. Browse the application normally with the proxy on. Review the history: hosts, endpoints, parameters, cookies, how login and logout work.
  2. Look at what the client controls. Hidden fields, IDs, roles, prices, cookies, JSON bodies and headers are all attacker-controlled. See web security basics.
  3. Test one idea at a time in Repeater and note the request and response that prove each result.
  4. Automate only what needs it, with caps on speed and volume.
  5. Document as you go: time, request, response, impact, fix. Screenshots alone are not enough. Reporting guidance is in Reporting.
  6. Clean up: clear test data, remove the CA certificate and delete saved project files that contain sessions or personal data.

What defenders should take from this

Anything the browser can send, an attacker can send. Hidden fields, client-side validation and disabled buttons are not controls. Enforce authorization, input validation and business rules on the server. Log and rate-limit so that systematic probing is noticed, and use the same proxy in your own testing so you find these issues first.

Modules, extensions and limits

Older descriptions of Burp talk about the Spider (now called the crawler) that maps an application and the Extender (now the Extensions tab, with the BApp Store) that adds features. Useful extensions include Autorize (compares responses of different users to find broken access control), Turbo Intruder (a scripting engine for sending very many requests quickly, helpful for testing race conditions), Active Scan++ (extra scanner checks) and JSON Beautifier (readable JSON bodies).

Limitations: the free Community edition lacks the scanner and has a throttled Intruder, the tool can miss logic flaws that need human thinking, and large applications produce enormous histories that need filtering. Always keep the target scope set so the proxy does not touch other sites.

OWASP ZAP: terms and workflow

ZAP is the free open-source counterpart. Its vocabulary: a context defines which URLs belong to the application and how users log in; a session stores the current state; the spider (and the AJAX spider for JavaScript-heavy pages) discovers URLs; the passive scan inspects traffic without sending extra requests; the active scan sends attack-like requests; alerts are findings ranked by risk and confidence. Run active scans only on systems you may test, and prefer a staging copy.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why must a testing proxy's CA certificate be trusted by the browser?

    HTTPS is encrypted end to end. A trusted proxy certificate lets the proxy decrypt, inspect and re-encrypt traffic. Remove it after testing.
  2. 2. Which tool is best for changing one parameter and comparing the response?

    Repeater replays and edits individual requests, perfect for testing access control and input handling one change at a time.
  3. 3. What does the Sequencer analyze?

    Predictable tokens let attackers guess other users' sessions, so token randomness is worth measuring.
  4. 4. Why should automated tools such as Intruder be used with caps and delays?

    Automation multiplies requests. Without limits it can cause outages or data changes, which is not acceptable in authorized testing.

Summary

  • An intercepting proxy lets you see, change and replay what your browser sends; Burp Suite is a popular example.
  • Setup means a local listener, a browser profile using it, a trusted proxy CA certificate (removed afterward) and a defined scope.
  • Repeater tests single changes, Intruder automates variations with limits, Sequencer measures token randomness, Decoder translates encodings, and scanners and extensions add coverage.
  • Work in a loop: observe, modify one thing, compare, document.
  • Anything the client can send can be altered, so enforce checks on the server.

Next: SQL Injection: Understanding and Preventing It