Skip to main content
PProfileMatch
← Path

OWASP Top 10 · OWASP Top 10: Broken Access Control and Injection Explained

0 XP
  1. 1 current stop: learning
  2. 2 upcoming
  3. 3 upcoming
  4. 4 upcoming
  5. 5 upcoming

Finish after stop 5

Stop 1 of 5 · Block of flats: the lift panel

Trick to keep in mind+3 XP

Logged in answers 'who are you'; allowed answers 'is this record yours'.

Authentication proves identity, but every request that names a record still needs its own question: may this person touch this one? A page that changes only the number in the URL and returns a stranger's data has skipped that step. Hiding buttons, encrypting the connection or throttling requests does nothing to answer it. The check must run on the server, per record.

Read it once, then a question tests whether the trick stuck.