Course contentsShow
← Security
Lesson 1029 of 3,05221. Web Security - API SecurityFree lesson

API3:2023 - Broken Object Property Level Authorization

Learning how mass assignment and excessive data exposure allow unauthorized access to or modification of object properties.

API3:2023 - Broken Object Property Level Authorization

You'll learn how attackers exploit weak property-level controls to view or modify object fields they shouldn't access.

What Is Broken Object Property Level Authorization?

While Broken Object Level Authorization (BOLA) controls which objects a user can access, Broken Object Property Level Authorization controls which properties (fields) within an object they can read or modify. This vulnerability occurs when APIs fail to validate authorization at the granular property level, allowing attackers to access sensitive fields or modify restricted attributes.

This encompasses two key attack vectors you've already studied:

Mass Assignment (Writing Properties)

An attacker sends extra fields in a request to modify object properties they shouldn't control. For example, submitting "isAdmin": true alongside legitimate profile updates.

PUT /api/users/123
Content-Type: application/json

{
  "name": "Alice",
  "email": "alice@example.com",
  "isAdmin": true,
  "accountBalance": 99999
}

The API blindly assigns all submitted properties without checking authorization, elevating privileges or manipulating business logic.

Excessive Data Exposure (Reading Properties)

The API returns entire objects with sensitive fields a user shouldn't see:

{
  "id": 123,
  "name": "Alice",
  "email": "alice@example.com",
  "ssn": "123-45-6789",
  "creditCard": "4111111111111111",
  "internalNotes": "VIP customer, do not charge fees"
}

Regular users receive admin-only fields, internal identifiers, or PII belonging to others—simply because the API didn't filter response properties based on the requester's role.

Think of It Like Hotel Room Access

You're authorized to enter your hotel room (object-level), but you shouldn't access the manager's master key hidden in the drawer (property-level). Broken property authorization is like the hotel not checking what items you touch once inside.

Key Takeaway: API3:2023 requires validating authorization for every individual property users read or write, not just the objects themselves—implement explicit allowlists for input acceptance and output filtering based on user roles.