eWPTXv3 - Notes
GitHubPortfolioTwitter/X MediumCont@ctHome
  • 📝eWPTXv3
    • Web Application Penetration Testing Methodology
      • 1.1 Introduction to Web App Security Testing
        • 1.1.1 Web Application
        • 1.1.2 Web App Architecture
        • 1.1.3 HTTP/HTTPS
      • 1.2 Web App Pentesting Methodology
    • Web Application Reconnaissance
      • 2.1 Information Gathering
        • 2.1.1 DNS Recon
          • 2.1.1.1 DNS Zone Transfer
          • 2.1.1.2 Subdomain Enumeration
        • 2.1.2 WAF Recon
      • 2.2 Passive Crawling & Spidering
      • 2.3 Web Server Fingerprinting
        • 2.3.1 File & Directory Brute-Force
      • 2.4 Web Proxies
        • 2.4.1 Burp Suite
        • 2.4.2 OWASP ZAP
    • Authentication Attacks
      • 6.1 HTTP Attacks
        • 6.1.1 HTTP Method Tampering
        • 6.1.2 Attacking HTTP Authentication
      • 6.2 Session Attacks
        • 6.2.1 Session Hijacking
        • 6.2.2 Session Fixation
        • 6.2.3 Session Hijacking via Cookie Tampering
      • 6.3 JWT Attacks
      • 6.4 CSRF
    • Injection Vulnerabilities
      • 4.1 Command Injection
      • 4.2 Cross-Site Scripting (XSS)
        • 4.2.1 XSS Anatomy
        • 4.2.2 Reflected XSS
        • 4.2.3 Stored XSS
        • 4.2.4 DOM-Based XSS
        • 4.2.5 Identifying & Exploiting XSS with XSSer
      • 4.3 ​SQL Injection (SQLi)
        • 4.3.1 DB & SQL Introduction
        • 4.3.2 SQL Injection (SQLi)
        • 4.3.3 In-Band SQLi
        • 4.3.4 Blind SQLi
        • 4.3.5 NoSQL
        • 4.3.6 SQLMap
        • 4.3.7 Mitigation Strategies
    • API Penetration Testing
      • 5.1 API Testing
    • Server-Side Attacks
      • 6.1 Server-side request forgery (SSRF)
      • 6.2 Deserialization
      • 6.3 ​File & Resource Attacks
        • 6.1 File Upload Vulnerability
        • 6.2 Directory Traversal
        • 6.3 File Inclusion (LFI and RFI)
          • 6.3.1 Local File Inclusion (LFI)
          • 6.3.2 Remote File Inclusion (RFI)
        • 6.4 CMS Pentesting
          • 6.4.1 Wordpress, Drupal & Magento
    • Filter Evasion & WAF Bypass
      • 7.1 Obfuscating attacks using encodings
    • 📄Report
      • How to write a PT Report
  • 🛣️RoadMap / Exam Preparation
  • 📔eWPTX Cheat Sheet
Powered by GitBook
On this page
  • Session Hijacking
  • Phase 1 - Token Acquisition
  • Phase 2 - Impersonation
  • Impact
  1. eWPTXv3
  2. Authentication Attacks
  3. 6.2 Session Attacks

6.2.1 Session Hijacking

Session Hijacking

Session Hijacking, also known as session theft, is a security attack where an attacker illegitimately takes over a user's active session on a web app.

In this type of attack, the attacker gains unauthorized access tot he user's session token or identifier, allowing them to impersonate the victim and perform actions on their behalf.

Phase 1 - Token Acquisition

  • Session Prediction: predicting or guessing the session token, especially if it's predictable or lacks sufficient randomness.

  • Session Sniffing: intercepting the session token as it's transmitted over an unsercured network, such as an open Wi-Fi hotspot

  • Cross-Site Scripting (XSS): exploiting a vulnerability in the web app to inject malicious JavaScript code into a victim's browser, which can steal the session token.

Phase 2 - Impersonation

When the attacker has the session token, they can impersonate the victim by presenting this token during requests to the web app.

The app not protected by hijacking, treats the attacker as the authenticated user.

Impact

  • Data Theft: access and steal the victim's sensitive data, such as personal info, financial details or confidential documents.

  • Account Takeover: change the victim's account setting, passwords, or email address, locking the victim out of their account.

  • Malicious Transactions: conduct unauthorized transactions, make purchases, or manipulate the victim's data.

Previous6.2 Session AttacksNext6.2.2 Session Fixation
📝