tbhm:12_idor
This is an old revision of the document!
Table of Contents
Insecure Direct Object References
IDOR Overview
To be continued…
Zseano IDOR Additions
- Try integers even when you see GUIDs – server may accept both formats
- Inject
“id”:“1”into JSON POST bodies even when not normally present - Hunt mobile apps first – they use APIs directly, usually weaker
- Look specifically for PUT requests – they modify data by ID
- Blind IDORs: no visible response but action still occurs (check email, data changes)
- Change file type extension on resource endpoint:
.jsonvs.xmlvs.csv
High-value targets: password changes, private documents, receipts, DM systems, payment views.
tbhm/12_idor.1778749158.txt.gz · Last modified: by drew
