Broken Access Control
Restrictions on what authenticated users are allowed to do are not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc.
|Threat Agents||Attack Vectors||Security Weakness||Technical Impacts||Business Impacts|
|Application Specific||Exploitability => Easy||Prevalence => Common||Detectability => Average||Impact => Severe||App/Business Specific|
|Considerthe types of authorized users of your system. Are users restricted to certain functions and data? Are unauthenticated users allowed access to any functionality or data?||Attackers,who are authorized users, simply change a parameter value to another resource they aren’t authorized for. Is access to this functionality or data granted?||For data, applications and APIsfrequentlyuse the actual name or key of an object when generating web pages. For functions, URLs and function names are frequently easy to guess. Applications and APIs don’t always verify the user is authorized for the target resource. This results in an access control flaw. Testers can easily manipulate parameters to detect such flaws. Code analysis quickly shows whether authorization is correct.||Such flaws can compromise all the functionality or data that is accessible. Unless references are unpredictable,or access control is enforced, data and functionality can be stolen, or abused.||Consider the business value of the exposed data and functionality. Also consider the business impact of public exposure of the vulnerability.|
The best way to find out if an application is vulnerable to access control vulnerabilities is to verify that all data and function references have appropriate defenses.
To determine if you are vulnerable, consider:
- For data references, does the application ensure the user is authorized by using a reference map or access control check to ensure the user is authorized for that data?
For non-public function requests, does the application ensure the user is authenticated, and has the required roles or privileges to use that function?
Code review of the application can verify whether these controls are implemented correctly and are present everywhere they are required.
- Manual testing is also effective for identifying access control flaws.
- Automated tools typically do not look for such flaws because they cannot recognize what requires protection or what is safe or unsafe.
Preventing access control flaws requires selecting an approach for protecting each function and each type of data (e.g., object number, filename).
- Check access. Each use of a direct reference from an untrusted source must include an access control check to ensure the user is authorized for the requested resource.
- Use per user or session indirect object references.
- This coding pattern prevents attackers from directly targeting unauthorized resources.
- For example, instead of using the resource’s database key, a drop down list of six resources authorized for the current user could use the numbers 1 to 6 to indicate which value the user selected.
- OWASP’s ESAPI includes both sequential and random access reference maps that developers can use to eliminate direct object references.
- Automated verification. Leverage automation to verify proper authorization deployment.
- This is often custom.
Example Attack Scenarios
The application uses unverified data in a SQL call that is accessing account information:
pstmt.setString( 1, request.getParameter("acct"));ResultSet results = pstmt.executeQuery( );
An attacker simply modifies the ‘acct’ parameter in the browser to send whatever account number they want. If not properly verified, the attacker can access any user’s account.
An attacker simply force browses to target URLs.
Admin rights are also required for access to the admin page.
If an unauthenticated user can access either page, it’s a flaw. If a non-admin can access the admin page, this is also a flaw