Parameter Tampering in IDOR Attacks
What you'll learn: How attackers modify request parameters to exploit IDOR vulnerabilities and access unauthorized resources.
The Core Idea
Parameter tampering in IDOR (Insecure Direct Object Reference) attacks involves manipulating the values sent in HTTP requests to access objects or data belonging to other users. Attackers modify parameters in URLs, POST request bodies, or even hidden form fields to reference objects they shouldn't have access to.
Think of it like changing the apartment number on a package delivery slip. If the building doesn't verify you actually live in that apartment, you could receive someone else's mail just by writing a different number.
Common Tampering Points
URL Parameters: The most visible target. An attacker might change /profile?user_id=123 to /profile?user_id=124 to view another user's profile.
Request Body Parameters: In POST requests, attackers can modify JSON or form data fields like {"document_id": 789} to try different values.
Hidden Form Fields: HTML forms sometimes include hidden fields like <input type="hidden" name="account_id" value="456">. These can be modified using browser developer tools before submission.
HTTP Headers: Custom headers containing identifiers (like X-User-ID) can also be tampered with if the server trusts them without proper authorization checks.
Why It Works
This attack succeeds when applications:
- Use predictable identifiers (sequential numbers, GUIDs without authorization)
- Trust client-supplied parameters without server-side validation
- Check authentication (who you are) but skip authorization (what you can access)
The application assumes only legitimate users will submit legitimate IDs, but attackers can easily modify any parameter before sending the request.
Key Takeaway: Parameter tampering exploits the gap between authentication and authorization—always validate that the authenticated user has permission to access the specific object referenced by any client-supplied identifier, regardless of where that identifier appears in the request.