Business Logic Vulnerability

Overview

A Business Logic Vulnerability is a weakness that lets an attacker misuse a valid feature sequence, rule, state transition, pricing assumption, or operational workflow to produce an unauthorized outcome. The control exists to prevent APIs and applications from allowing unauthorized data access, privileged functions, unsafe state changes, or execution through defective design or implementation. It may use well-formed requests and valid credentials, so generic scanners and input validation can miss it. It should be interpreted alongside Payment Processing Boundary because the concepts can affect the same decision without representing the same control, event, or risk.

The workflow starts with explicit trust boundaries, identities, objects, fields, functions, states, and allowed transitions. Server-side controls validate every request, use restrictive schemas, calculate authoritative values, and reject operations that violate authorization, sequence, rate, content, or business rules. In this context, prevention requires threat modeling of incentives and abuse cases, server-side state enforcement, atomic limits, idempotency, independent value calculation, concurrency testing, anomaly monitoring, and review of exceptional or recovery paths.

It should connect the term to Idempotency Key where that relationship changes access, transaction treatment, investigation, communication, or recovery.

Testing should include positive and negative authorization cases, multiple roles and tenants, malformed and replayed requests, concurrency, version changes, nested data, recovery paths, and production-like configurations. Logs should connect principal, request, resource, decision, error, and resulting state without recording secrets.

Useful measures include endpoint coverage, failed authorization tests, vulnerable versions, time to remediate, abuse attempts, error and rejection rates, recurring defect classes, and differences between specification and deployed behavior.

The relationship with Control Testing should be documented where it affects residual risk or control ownership.