CPSA ยท Web testing techniques
Parameter manipulation with an intercepting proxy
Intercepting and altering GET, POST, cookie and hidden parameters.
Key points
- An intercepting proxy such as Burp Suite sits between browser and server so a tester can pause, read and edit each request before it is sent.
- Everything the client sends is under the user's control: query-string and POST parameters, cookies, headers and hidden form fields.
- Client-side checks (disabled fields, JavaScript validation, hidden prices or roles) are only convenience and must be re-enforced on the server.
Practice questions
Why can a hidden form field not be trusted for security decisions?
- It is encrypted by the browser
- The client controls the value and can change it before submission
- It is removed by HTTPS
- It is read-only for proxies
Show answer
Answer: B. The client controls the value and can change it before submission
Hidden only means not displayed; the value is sent by the client and can be edited with a proxy or developer tools.
Which request elements can a tester alter with an intercepting proxy?
- Query-string parameters
- Cookie values
- POST body fields, including hidden ones
- Server-side session store contents directly
- The server's response before it is generated
Show answer
Answer: A. Query-string parameters, B. Cookie values, C. POST body fields, including hidden ones
Everything in the request is client-controlled: URL parameters, cookies and body fields. The server's own database contents are not part of the request.
A form field marked disabled or readonly in the HTML cannot be changed by a user.
Show answer
Answer: False
False. These attributes only affect the browser UI; the request can be edited in a proxy or recreated manually.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
