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

JWT

JWT Attacks

Description

JWT (JSON Web Token) attacks exploit vulnerabilities in the implementation or usage of JWTs, allowing attackers to forge tokens, manipulate claims, or perform other malicious actions.

Example with Scenario

Scenario: A web application uses JWTs for user authentication. An attacker can exploit weak signing algorithms or insecure storage to forge tokens and gain unauthorized access.

Payloads and Test Cases

Payloads

  1. None Algorithm Attack:

    {
      "alg": "none"
    }
  2. Brute Force HMAC Secret:

    {
      "header": {
        "alg": "HS256",
        "typ": "JWT"
      },
      "payload": {
        "user": "admin"
      },
      "signature": "generated_signature"
    }
  3. Claim Manipulation:

    {
      "header": {
        "alg": "HS256",
        "typ": "JWT"
      },
      "payload": {
        "user": "attacker",
        "admin": true
      },
      "signature": "generated_signature"
    }

Test Cases

  1. None Algorithm Attack:

    • Payload:

      {
        "alg": "none"
      }
    • Test Case:

      # Create a JWT with the 'none' algorithm
      jwtToken = createJWT({"alg": "none"}, {"user": "admin"}, "")
      # Send the token to the server
      sendJWTToServer(jwtToken)
      # Verify if the server accepts the token without validation
      checkAdminAccessGranted()
  2. Brute Force HMAC Secret:

    • Payload:

      {
        "header": {
          "alg": "HS256",
          "typ": "JWT"
        },
        "payload": {
          "user": "admin"
        },
        "signature": "generated_signature"
      }
    • Test Case:

      # Generate a JWT with a known weak secret
      jwtToken = createJWT({"alg": "HS256"}, {"user": "admin"}, "weak_secret")
      # Send the token to the server
      sendJWTToServer(jwtToken)
      # Verify if the server accepts the token
      checkAdminAccessGranted()
  3. Claim Manipulation:

    • Payload:

      {
        "header": {
          "alg": "HS256",
          "typ": "JWT"
        },
        "payload": {
          "user": "attacker",
          "admin": true
        },
        "signature": "generated_signature"
      }
    • Test Case:

      # Create a JWT with manipulated claims
      jwtToken = createJWT({"alg": "HS256"}, {"user": "attacker", "admin": True}, "valid_secret")
      # Send the token to the server
      sendJWTToServer(jwtToken)
      # Verify if the server grants admin access
      checkAdminAccessGranted()

Mitigation

  1. Use Strong Secrets:

    • Use strong, random secrets for signing JWTs.

    • Avoid using weak or easily guessable secrets.

  2. Validate Tokens Properly:

    • Always validate the token signature and claims.

    • Reject tokens with invalid or missing signatures.

  3. Enforce Algorithm Constraints:

    • Enforce the use of secure algorithms (e.g., HS256, RS256).

    • Reject tokens with the 'none' algorithm or other weak algorithms.

  4. Secure Token Storage:

    • Store JWTs securely on the client side (e.g., HTTP-only cookies).

    • Avoid storing tokens in local storage or other insecure places.

  5. Implement Expiry and Revocation:

    • Implement token expiry and refresh mechanisms.

    • Provide a way to revoke tokens when necessary.

PreviousXPath InjectionNextParameter Pollution

Last updated 10 months ago