detecting-broken-object-property-level-authorization

# Detecting Broken Object Property Level Authorization ## Overview Broken Object Property Level Authorization (BOPLA), classified as API3:2023 in the OWASP API Security Top 10, combines two related vulnerability classes: Excessive Data Exposure (API returning more data than needed) and Mass Assignment (API accepting more data than intended). Even when APIs enforce object-level authorization correctly, they may fail to control which specific properties of an object a user can read or modify. Attackers exploit this by reading sensitive properties from API responses or injecting additional properties into request bodies to modify fields they should not have access to. ## When to Use - When investigating security incidents that require detecting broken object property level authorization - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - Target API with endpoints that return or accept object data - API documentation or schema (OpenAPI spec preferred) - Burp Suite or Postman for API request manipulation - Multiple user accounts with different privilege levels - Python 3.8+ with requests library for automated testing - Authorization to perform security testing ## Vulnerability Patterns ### Excessive Data Exposure The API returns object properties the client does not need: ```json // GE...