312-50 ยท Web servers and web applications
Authentication, authorization and access control attacks
Credential attacks, weak reset flows, broken access control, IDOR, privilege escalation in apps, MFA bypass concepts.
Key points
- Authentication proves who you are. Authorization decides what you may do.
- Attacks: credential stuffing, brute force, weak password-reset flows, session fixation, MFA bypass through fatigue or flawed fallback paths.
- Broken access control: reaching others' data (IDOR) or higher functions (privilege escalation).
- Cause: the server trusts client-supplied identifiers instead of checking permissions on every request.
Practice questions
What does IDOR stand for?
- Insecure Direct Object Reference
- Internal Data Output Routine
- Indirect Domain Origin Request
- Integrated Digital Object Registry
Show answer
Answer: A. Insecure Direct Object Reference
Insecure Direct Object Reference: the app exposes an internal identifier and does not check that the caller may use it.
Which are weaknesses in a password-reset flow?
- Predictable, sequential reset tokens
- Single-use tokens that expire quickly
- Reset tokens that never expire
- Sending the link only to the registered email
- Rate limiting reset requests
Show answer
Answer: A. Predictable, sequential reset tokens, C. Reset tokens that never expire
Predictable tokens and tokens that never expire let attackers take over accounts. Single-use random expiring tokens are the safe design.
True or false: hiding the admin menu from regular users is enough to protect admin functions.
Show answer
Answer: False
False. Hiding UI is not access control; the server must enforce authorization on every admin endpoint because attackers can request URLs directly.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
