Day 5 of 2160 minShell WalkerHands-on lab
Day 5: Reading Traffic: Burp Suite and an AI Second Opinion
Taught by Mr Elite Updated
By the end of today you can
- Configure Burp Suite Community Edition and capture browser traffic in HTTP history
- Redact a request and ask an assistant to interpret it, then check its claims
- Spot where your input lands in a response and explain why it is reflected
- Confirm a reflected XSS flaw in the SecurityElites lab with a payload that executes
Warm-up
Answer from memory first, then tap to check. Recalling yesterday is what makes it stick.
In the Day 4 pipeline (scope, redact, draft, verify, record), which stage is the only one where the assistant is involved?
Draft. Everything else is done by you.
What should happen to a plan step that breaks scope?
Delete it. Do not negotiate with the scope.
You have a test plan from yesterday. Now you need to see what the application actually says to your browser. A browser hides almost everything: headers, cookies, the exact bytes of a response. Burp Suite sits in the middle and shows you all of it.
Today you will capture real traffic, ask an assistant to explain one request, and then prove the one thing the assistant cannot prove for you: that your input comes back in the page and runs as JavaScript. The assistant gives an opinion. The lab gives evidence.
What Burp does and what reflected XSS is
Burp Suite is an intercepting proxy. A proxy is a program that sits between your browser and a website and passes traffic through. Because Burp is in the middle, it can record every request and response. You then read them, replay them and change them.
Reflected cross-site scripting (XSS) happens when an application takes something you sent, such as a search term, and writes it straight into the response page without making it safe. If the page treats your text as HTML or script, your text runs in the victim's browser. It is called reflected because the input bounces straight back in the same response, rather than being stored.
Think of a shop assistant who repeats your order back on a printed receipt. If you say something odd and the receipt printer obeys it as an instruction, that is the flaw. A safe app prints your words as plain text. A vulnerable one lets the words act as page code. Burp lets you read the receipt exactly as printed, not as the browser tidies it up.
- HTTP history
- The Burp tab that lists every request and response that passed through the proxy, in order.
- Reflection
- Your input appearing somewhere in the response body.
- Injection context
- The place in the page where your input lands, for example between tags or inside an attribute. It decides which payload works.
- Payload
- The input you craft to test or prove the flaw.
Set up Burp and capture traffic
We use Burp's built-in browser, because it needs no certificate or proxy settings. Only use it on the SecurityElites lab or your own machine today. Never point it at a site that is outside scope.
Quick check
Why do we turn Intercept off for now?
Intercept holds each request for editing. With it off, traffic is still logged in HTTP history without stalling.
Watch me do it: capture, redact, ask, verify
Here is the full loop I want you to repeat. I will use the lab search box. Follow along in your own Burp. The lab is a practice target, so the request holds no real secrets, but we redact anyway to build the habit from Day 2.
Your request will look broadly like the one below. The parameter name may differ in the lab, so read yours rather than copying mine. The point is the shape: a method and path carrying your term, then headers, then a cookie you must hide.
GET /search?q=banana HTTP/1.1
Host: bookshop.lab
User-Agent: Mozilla/5.0 ...
Accept: text/html
Cookie: session=REDACTEDHere is a redacted HTTP request from a practice lab I am allowed to test.
[paste request]
Explain each header in one line. Tell me which parameter is user controlled, where it might be reflected in the response, and what I should test first. Mark anything you are unsure about.When the answer comes back, you should see line by line explanations of Host, User-Agent and the rest, plus a guess that q is user controlled. That guess matches what you saw in Burp, so it is cheap to trust. Anything about how the server encodes output is only a guess until you test it. Circle those claims for the next section.
Your turn: the reflected XSS lab
Now you prove it. The lab below is BookShop, a deliberately vulnerable site made for this. Use Burp to watch what you send and what returns. Test the reflection with a harmless marker first, then work towards a payload that fits the context you found. Everything here stays inside the practice lab.
zq7<b>xQuick check
You search for zq7x and the raw response contains zq7<b>x. What does that tell you?
Encoded output means the browser shows the characters as text instead of parsing them as tags.
Common slips
Most trouble today comes from a few predictable habits. The mistakes section below lists them, and the fixes are quick. Read it before you start the lab if you get stuck.
If you are stuck on a blank page after submitting, check Intercept first. If your marker is missing from the response, you may be searching the wrong tab or the wrong request, so sort HTTP history by newest and look again. And if the alert never appears, look at what sits immediately around your marker in the Raw view before you try anything new.
Your turn
Reflected XSS
The BookShop search box echoes your query into the page without sanitising it. It is a safe, isolated target built for exactly this practice, so it is the right place to turn a reflection you can see in Burp into script execution you can prove.
What to try
What to notice
- The request path and parameter name that carry your search term
- Exactly which characters, if any, the app changes before reflecting them
- The difference between seeing your text in the source and seeing it run in the browser
If it did not work
Using a normal browser, so Burp history stays empty
Close it and use the browser launched from Proxy, then Open browser.
Treating the assistant's explanation as proof that the flaw exists
Use it for ideas only. The flaw is confirmed when your payload runs in the lab.
Pasting the raw request with cookies into the assistant
Replace sensitive values with REDACTED before copying, and check the pasted text once more.
Judging reflection by the rendered page only
Read the raw Response tab in Burp. The browser can hide how your input was encoded.
Recap
- Burp records traffic so you can read exactly what the browser and server exchange
- HTTP history is where you find the request, the response and your reflection
- Injection context decides which payload will work
- An assistant can explain a request and suggest tests, but only your test proves a flaw
- Redact before you paste, every time
- Reflection is a lead; script execution is the evidence
Cheat sheet
Proxy > HTTP history- Chronological list of captured requests and responses
Intercept off- Record traffic without pausing each request
Open browser- Burp's built-in Chromium that is already proxied
Response search box- Find where your marker lands in the reply
< in the response- Output is HTML-encoded, so that context is probably safe
REDACTED- Placeholder for cookies and tokens before sharing
Before the next day
Mission: Evidence of one confirmed XSS
Solve the lab, and keep proof that shows both the traffic and the result. Then judge the assistant's help honestly, because that habit feeds the Day 19 report writing.
About 30 min
You are done when: A folder holding two screenshots (Burp request and executed payload) plus a note.txt with two lines on what the assistant got right.
Want more? Find the same reflection in Burp Repeater by sending the request there and editing the parameter, then record how the response changes for three different inputs.
Quiz
4 questions. Your score is saved with your progress.
1. What is the main advantage of Burp's HTTP history over just using the browser?
The browser hides raw details. Burp lets you read the exact bytes, which is where encoding and context become visible.
2. You see your marker in the response, but no script runs. What is the best next step?
Reflection alone is not a finding. Context and encoding decide whether a payload can execute.
3. Why redact a request before pasting it into an assistant?
Sensitive values can leak access to real accounts. Redaction keeps the useful structure and removes the risk.
4. The assistant says a parameter is definitely vulnerable. How should you treat that?
Treat model output as a hypothesis. Your test result, pasted and recorded, is the proof, as in Day 4.
Finish the day
Mark the day complete to save your progress.
Next: Day 6 takes the same flaw further: the DOM, attributes and other injection contexts, and how to choose a payload that fits each one. Today's habit of reading the context in Burp is exactly what you will rely on.
Your notes
Private to this device. Write what you want to remember from today.