Concepts / Web access and file flaws

Web access and file flaws

Insecure direct object reference

Also called IDOR, broken object-level authorisation, BOLA

Reaching another user's data by changing an id, filename or key in a request the server never checks you own.

Signed in is not the same as allowed
Signed in is not the same as allowed

The server checks that someone is signed in, but not that the account named in the request is theirs. Changing the id returns another user's record.

An insecure direct object reference (IDOR) lets a user reach another user's data by changing an id in a request. The request names the object, like /account?id=2, and the server returns it after checking only that you are logged in, so id=1 returns someone else's record. Random ids only make guessing harder. The fix is a server-side check, on every request, that this session may have that object: see [[broken-access-control]].

See it on real machines

Read next

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab