IDOR
Insecure Direct Object References (IDOR) arise from weak access controls in the back end, allowing attackers to access or modify unauthorized data. While exposing internal object references isn't inherently a vulnerability, the lack of proper access control makes IDOR dangerous.
IDOR TYPES
IDOR information disclosure: this is where attackers access private user data such as personal files and credit card info. this IDOR can lead to account takeover
IDOR insecure function calls: this is where attackers elevate privileges to gain admin access. this IDOR leads to full system compromise
MITIGATION
build an object-level access control system
map the RBAC to all objects and resources and assign each user a role that has certain privileges
use secure references for objects when storing and calling them.
never use object references in clear text or simple patterns (e.g., uid=1). always use strong and unique references, like salted hashes or
UUID
's. lastly, never calculate hashes on the front-end
Last updated