CWE-862
Missing Authorization
AI Translation Available
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Status
incomplete
Abstraction
class
Likelihood
high
Affected Platforms
AI/ML
Web Server
Database Server
Technical Details
AI Translation
Common Consequences
confidentiality
integrity
access control
availability
Impacts
read application data
read files or directories
modify application data
modify files or directories
gain privileges or assume identity
bypass protection mechanism
dos: crash, exit, or restart
dos: resource consumption (cpu)
dos: resource consumption (memory)
dos: resource consumption (other)
Detection Methods
automated static analysis
automated dynamic analysis
manual analysis
manual static analysis - binary or bytecode
dynamic analysis with automated results interpretation
dynamic analysis with manual results interpretation
manual static analysis - source code
automated static analysis - source code
architecture or design review
Potential Mitigations
Phases:
architecture and design
system configuration
installation
Descriptions:
•
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
•
For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
•
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
•
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
•
Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.