API1:2023 - Broken Object Level Authorization (BOLA)
What You'll Learn
You'll understand why BOLA tops the OWASP API Security Top 10 and how attackers exploit weak object-level access controls to view or manipulate data they shouldn't touch.
The Crown Jewel of API Vulnerabilities
Broken Object Level Authorization (BOLA), designated as API1:2023 in OWASP's latest ranking, remains the most critical and prevalent API security vulnerability. When an API fails to verify that the authenticated user has permission to access a specific object, attackers can simply change object identifiers (IDs) in requests to access other users' data.
Why It's Number One
BOLA ranks first because it's:
- Widespread: Found in most APIs during security testing
- Easy to exploit: Requires only changing IDs in requests
- High impact: Direct access to sensitive data or resources
Think of it like a hotel where your keycard opens your room (authentication works), but because the system doesn't check room ownership, you can try other room numbers and the doors open (authorization fails).
The Core Problem
APIs typically authenticate users successfully but then trust client-supplied object IDs without verifying ownership. An attacker authenticated as User A can manipulate requests like:
GET /api/users/123/profile → GET /api/users/456/profile
If the API only checks "Is this user logged in?" rather than "Does this user own profile 456?", authorization is broken at the object level.
Real-World Impact
BOLA enables attackers to:
- Read other users' personal data, orders, or documents
- Modify resources belonging to others
- Delete objects they don't own
- Enumerate all objects by iterating through IDs
Key Takeaway: BOLA is API1:2023 because most APIs authenticate users but fail to verify they own the specific objects being accessed—always validate that the authenticated user has rights to the requested resource, not just that they're logged in.