0x211 - Update/Read Parallel Intruder
0x211 - Update/Read Parallel Intruder
Pentest Tips & Tricks
A01 - Broken Access Control
A01 - Broken Access Control
A02 - Cryptographic Failures
A02 - Cryptographic Failures
A03 - Injection Attacks
A03 - Injection Attacks
A04 – Insecure Design
A04 – Insecure Design
A05 – Security Misconfiguration
A05 – Security Misconfiguration
A06 – Vulnerable Components
A06 – Vulnerable Components
A07 – Identification and Authentication Failures
A07 – Identification and Authentication Failures
Recon & Attack Surface
Recon & Attack Surface
Tooling & Automation
Tooling & Automation
Creative, Strategic, and Mindset
Creative, Strategic, and Mindset
Bug Bounty $$$
Bug Bounty $$$
AI/ML/LLM/MCP
AI/ML/LLM/MCP
Latest Tips & Tricks
Latest Tips & Tricks
Every once in a while I come across the same scenario which is difficult and frustrating to test:
Inject payload in one endpoint (POST/PUT)
Check reflected payload in another endpoint (GET)
Each new injected payload overrides the previous one (!)
Therefore running a full intruder on the POST/PUT endpoint and then using the GET endpoint will only be relevant for the last payload sent.
So how do we fix this without manually sending the payload and reading the output with 2 different repeater tabs?
Solution
Have 2 different intruders (one for POST/PUT and one for GET)
Set the concurrent requests to 1
Set the delay between requests to 5000 milliseconds (5 seconds)
For the GET request, use the same payload list used in the POST/PUT, but place it in a dummy request header. This will make it possible for you to see which payload reflected a specific output and match the number of requests
Start the POST/PUT intruder
Wait ~2-3 seconds
Start the GET intruder
Once the attacks are done, you have the intruder results showing all reflected payloads, not just the last one sent: