Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Broken access control means people can see data they should not be able to see. OWASP describes access control as enforcing a policy so that users cannot act outside their given permissions. When it fails, information can leak or be changed or deleted, and actions beyond a user's permissions can be carried out.
How does broken access control work?
Imagine a hotel where your own room's key card also opens the door of the room next to it. Even if the front desk checked your identity correctly, it means little if the range the card allows was not decided properly.
IPA explains the problem in two forms. One is where authentication is missing, so that personal information can be seen with only an email address. The other is where the design takes a user ID or order number through the URL or similar, so that a logged-in person can act as someone else.
The first is a state in which the entrance has no check. The second is one where you can pass the entrance but nothing checks each room inside. The second is the common form also called IDOR. How to check is organized on the broken access control vulnerability page.
Why does broken access control matter?
In the 2021 OWASP Top 10, broken access control ranked first, up from fifth in the previous edition. In the data OWASP collected, it had the most occurrences of any category, over 318,000.
On a member or booking site, if one user can touch another's information, that is directly a leak of personal information. The screen can look normal, and the operator may not have checked what happens when a number in the URL is changed.
OWASP's preventive measures include denying everything by default except what is meant to be public, allowing access based on a check of ownership, and logging failures and notifying. IPA's root solution is to check, every time before data is operated on, that the operation is permitted. To compare your site against what a stranger can see, there is the free URL check.
Related terms
- IDOR: a flaw where changing a number is enough to see someone else's information
- Session management flaws: a flaw where weak management of the login state lets it be hijacked
- Two-factor authentication: a mechanism that asks for one more confirmation besides the password
- Vulnerability: a weakness in how a program is built or configured that can be an entrance for attack
Frequently asked questions
Does having a login screen prevent broken access control?
No. Login is authentication, which confirms who has arrived. Access control is authorization, which decides what that person may do, and it is a separate mechanism. Also check that a logged-in person cannot touch another person's data.
What should a member-site operator check first?
Check on the real screens whether a member can reach another member's information or an admin screen. Making two test accounts with different rights makes this easier to check. If you find a problem, tell us through a free consultation.
Next step
How to check permissions on a member site is organized on the broken access control vulnerability page, and the whole order for protecting login is in unauthorized access measures. The free URL check shows only what is visible from outside, and for help designing permissions, contact us.
Frequently asked questions
Does having a login screen prevent broken access control?
No. Login is authentication, which confirms who has arrived. Access control is authorization, which decides what that person may do, and it is a separate mechanism. Also check that a logged-in person cannot touch another person's data.
What should a member-site operator check first?
Check on the real screens whether a member can reach another member's information or an admin screen. Making two test accounts with different rights makes this easier to check. If you find a problem, tell us through a free consultation.