Broken Object-Level Authorization (BOLA)
What You'll Learn
You'll understand how APIs fail to properly check whether users should access specific data objects, leading to unauthorized information disclosure.
The Core Problem
Broken Object-Level Authorization (BOLA) occurs when an API doesn't verify that the authenticated user has permission to access the specific object they're requesting. The API might check that you're logged in, but it doesn't validate whether you personally should see that particular resource.
Think of it like a hotel key card system: your card proves you're a guest (authentication), but BOLA happens when the system doesn't verify you should access Room 305 specifically — any guest card opens any room.
How It Works in Practice
Consider an API endpoint like:
GET /api/orders/12345
A vulnerable API might:
- Verify you're logged in ✓
- Return order #12345 immediately ✗
It never checks: "Does this user own order #12345?"
An attacker simply changes the number:
GET /api/orders/12346
GET /api/orders/12347
...and accesses everyone else's orders. This is also called an Insecure Direct Object Reference (IDOR).
Why This Matters
BOLA is the #1 API security risk because:
- Every API endpoint returning user-specific data is potentially vulnerable
- Attackers can enumerate objects systematically
- It's often overlooked during development since authentication seems sufficient
Key Takeaway: Authentication proves who you are; authorization proves what you can access. BOLA vulnerabilities exist when APIs validate identity but fail to check object-level permissions for each specific resource requested.