Course contentsShow
← Security
Lesson 823 of 3,05217. Web Security - Authorization and Access ControlFree lesson

Identifying Privilege Escalation Vulnerabilities

Discover common patterns and indicators that signal potential privilege escalation opportunities.

Identifying Privilege Escalation Vulnerabilities

You'll learn: How to spot common patterns and red flags that indicate an application may be vulnerable to privilege escalation attacks.

What Makes Privilege Escalation Detectable?

Privilege escalation vulnerabilities leave telltale signs—patterns in code, API design, and user workflows that signal missing or weak authorization checks. Knowing what to look for turns a potential weakness into an identifiable security issue.

Common Indicators and Patterns

Hidden Admin Functions

Look for administrative endpoints or functions accessible at predictable URLs (like /admin/deleteUser or /api/promote) without visible links. Test if lower-privileged users can directly access them.

Role/Status Parameters in Requests

Watch for requests containing fields like isAdmin=false, role=user, or accountType=basic. These are prime tampering targets—try changing them to true, admin, or premium.

Inconsistent Authorization Checks

If some actions require verification but similar actions don't, that's a red flag. For example, if viewing a document checks permissions but editing doesn't.

Missing Re-Authentication for Sensitive Actions

Critical operations (password changes, role modifications) that don't require re-authentication or elevated confirmation may be exploitable if an attacker already has session access.

Mass Assignment Vulnerabilities

Forms or APIs that accept many parameters without filtering. An attacker might add role or permissions fields not intended for user modification.

Think of it like: A building where some doors have security guards checking IDs, but side doors are unlocked. The inconsistency reveals which paths are vulnerable.

Practical Detection Approach

  1. Map all user roles and their intended permissions
  2. Identify role-defining parameters in requests
  3. Test cross-role access by manipulating identifiers and parameters
  4. Check for missing authorization on administrative functions
  5. Look for multi-step processes where early steps check permissions but later steps don't

Key Takeaway: Privilege escalation vulnerabilities reveal themselves through inconsistent authorization checks, tamperable role parameters, and administrative functions lacking proper access controls.