Skip to content
StrikeOps

Broken Object Level Authorization (IDOR)

HighTypical severity Web applications and APIsCWE-639

01Description

The application returned or modified records belonging to other users when the record identifier in a request was changed, because it did not verify that the requesting user was authorized to access that object.

02Impact

An attacker with any valid account can access, and in some cases modify or delete, other users' data by changing identifiers. Where identifiers are sequential, the entire dataset can be retrieved.

03Severity

Typically

High

Typically High. Usually High. Critical where it exposes personal, financial or health data across all users, or allows modification or deletion of other users' records.

04How to verify

  1. 1Create two test accounts with the same role.
  2. 2Perform actions with account A and replay the requests with account B's session, changing only the object identifier.
  3. 3Test read, update and delete operations, and cross-tenant access in multi-tenant applications.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Enforce object-level authorization checks on the server for every request that accesses a record.
  2. 2Implement checks in a central authorization layer rather than per endpoint.
  3. 3Use unpredictable identifiers as defense in depth.
  4. 4Add cross-account tests to automated test suites.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo