broken access control
A flaw where the server lets a caller act on data or operations it should not, for example by trusting a user name the caller supplied or skipping an ownership check.
It lets attackers read or change other users’ data directly.
In more detail
It is the most common serious class of web and API vulnerability. Take identity only from verified credentials, take ownership from trusted resource data, and check authorization for every object and every field.
Related terms
- authorization — Deciding whether an already identified caller may perform a particular action on a particular resource.
- broken object level authorization — An API flaw where changing an identifier in a request, such as /tasks/2 instead of /tasks/1, lets a caller reach an object that belongs to someone else.
- deny by default — The rule that anything not explicitly allowed is refused, including when the facts needed to decide are missing.
Taught in
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC