PenTest Playbook
  • Welcome!
  • Web App Pentesting
    • SQL Injection
    • NoSQL Injection
    • XSS
    • CSRF
    • SSRF
    • XXE
    • IDOR
    • SSTI
    • Broken Access Control/Privilege Escalation
    • Open Redirect
    • File Inclusion
    • File Upload
    • Insecure Deserialization
      • XMLDecoder
    • LDAP Injection
    • XPath Injection
    • JWT
    • Parameter Pollution
    • Prototype Pollution
    • Race Conditions
    • CRLF Injection
    • LaTeX Injection
    • CORS Misconfiguration
    • Handy Commands & Payloads
  • Active Directory Pentest
    • Domain Enumeration
      • User Enumeration
      • Group Enumeration
      • GPO & OU Enumeration
      • ACLs
      • Trusts
      • User Hunting
    • Domain Privilege Escalation
      • Kerberoast
        • AS-REP Roast (Kerberoasting)
        • CRTP Lab 14
      • Targeted Kerberoasting
        • AS-REP Roast
        • Set SPN
      • Kerberos Delegation
        • Unconstrained Delegation
          • CRTP Lab 15
        • Constrained Delegation
          • CRTP Lab 16
        • Resource Based Constrained Delegation (RBCD)
          • CRTP Lab 17
      • Across Trusts
        • Child to Parent (Cross Domain)
          • Using Trust Tickets
            • CRTP Lab 18
          • Using KRBTGT Hash
            • CRTP Lab 19
        • Cross Forest
          • Lab 20
        • AD CS (Across Domain Trusts)
          • ESC1
            • CRTP Lab 21
        • Trust Abuse - MSSQL Servers
          • CRTP Lab 22
    • Lateral Movement
      • PowerShell Remoting
      • Extracting Creds, Hashes, Tickets
      • Over-PassTheHash
      • DCSync
    • Evasion
      • Evasion Cheetsheet
    • Persistence
      • Golden Ticket
        • CRTP Lab 8
      • Silver Ticket
        • CRTP Lab 9
      • Diamond Ticket
        • CRTP Lab 10
      • Skeleton Key
      • DSRM
        • CRTP Lab 11
      • Custom SSP
      • Using ACLs
        • AdminSDHolder
        • Rights Abuse
          • CRTP Lab 12
        • Security Descriptors
          • CRTP Lab 13
    • Tools
    • PowerShell
  • AI Security
    • LLM Security Checklist
    • GenAI Vision Security Checklist
    • Questionnaire for AI/ML/GenAI Engineering Teams
  • Network Pentesting
    • Information Gathering
    • Scanning
    • Port/Service Enumeration
      • 21 FTP
      • 22 SSH
      • 25, 465, 587 SMTP
      • 53 DNS
      • 80, 443 HTTP/s
      • 88 Kerberos
      • 135, 593 MSRPC
      • 137, 138, 139 NetBios
      • 139, 445 SMB
      • 161, 162, 10161, 10162/udp SNMP
      • 389, 636, 3268, 3269 LDAP
      • Untitled
      • Page 14
      • Page 15
      • Page 16
      • Page 17
      • Page 18
      • Page 19
      • Page 20
    • Nessus
    • Checklist
  • Mobile Pentesting
    • Android
      • Android PenTest Setup
      • Tools
    • iOS
  • DevSecOps
    • Building CI Pipeline
    • Threat Modeling
    • Secure Coding
      • Code Review Examples
        • Broken Access Control
        • Broken Authentication
        • Command Injection
        • SQLi
        • XSS
        • XXE
        • SSRF
        • SSTI
        • CSRF
        • Insecure Deserialization
        • XPath Injection
        • LDAP Injection
        • Insecure File Uploads
        • Path Traversal
        • LFI
        • RFI
        • Prototype Pollution
        • Connection String Injection
        • Sensitive Data Exposure
        • Security Misconfigurations
        • Buffer Overflow
        • Integer Overflow
        • Symlink Attack
        • Use After Free
        • Out of Bounds
      • C/C++ Secure Coding
      • Java/JS Secure Coding
      • Python Secure Coding
  • Malware Dev
    • Basics - Get detected!
    • Not so easy to stage!
    • Base64 Encode Shellcode
    • Caesar Cipher (ROT 13) Encrypt Shellcode
    • XOR Encrypt Shellcode
    • AES Encrypt Shellcode
  • Handy
    • Reverse Shells
    • Pivoting
    • File Transfers
    • Tmux
  • Wifi Pentesting
    • Monitoring
    • Cracking
  • Buffer Overflows
  • Cloud Security
    • AWS
    • GCP
    • Azure
  • Container Security
  • Todo
Powered by GitBook
On this page
  1. Web App Pentesting

Broken Access Control/Privilege Escalation

Description

Broken Access Control occurs when an application fails to enforce proper access restrictions, allowing unauthorized users to access or modify resources they shouldn't have access to. Privilege Escalation involves exploiting such weaknesses to gain higher-level access.

Example with Scenario

Scenario: A web application has an admin panel that should be accessible only to administrators. An attacker discovers that they can access the admin panel by directly navigating to the URL without proper authorization checks.

Payloads and Test Cases

Payloads

  1. Direct URL Access:

    /admin
  2. Parameter Manipulation:

    /user?role=admin
  3. Forced Browsing:

    /restricted/resource

Test Cases

  1. Direct URL Access:

    • Payload:

      /admin
    • Test Case:

      # Attempt to access the admin panel
      accessURL("/admin")
      # Verify if the application grants access
      checkAdminAccess()
  2. Parameter Manipulation:

    • Payload:

      /user?role=admin
    • Test Case:

      # Attempt to escalate privileges by modifying the role parameter
      accessURL("/user?role=admin")
      # Verify if the application grants admin privileges
      checkPrivilegeEscalation()
  3. Forced Browsing:

    • Payload:

      /restricted/resource
    • Test Case:

      # Attempt to access a restricted resource
      accessURL("/restricted/resource")
      # Verify if the application grants access
      checkAccessToRestrictedResource()

Mitigation

  1. Enforce Access Control:

    • Implement access control checks at the server-side for all sensitive actions.

    • Use role-based access control to enforce permissions.

  2. Use Secure Frameworks:

    • Use security frameworks that provide built-in access control mechanisms.

    • Ensure access control is consistently applied throughout the application.

  3. Parameter Validation:

    • Validate and sanitize parameters to ensure they cannot be manipulated to escalate privileges.

    • Use strong validation rules to prevent unauthorized access.

  4. Regular Audits:

    • Conduct regular security audits and penetration testing to identify and fix access control vulnerabilities.

    • Monitor access logs for suspicious activity.

PreviousSSTINextOpen Redirect

Last updated 11 months ago