eWPTv2
GitHubPortfolioTwitter/XMediumCont@ctHome
  • 📝eWPTv2
    • 1️⃣​1 - Introduction to Web App Security Testing
      • 1.1 Web Application
      • 1.2 Web App Architecture
      • 1.3 HTTP/HTTPS
      • 1.4 Web App Pentesting Methodology
    • 2️⃣2 - Web Fingerprinting and Enumeration
      • 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
    • 3️⃣3 - Web Proxies
      • 3.1 Burp Suite
      • 3.2 OWASP ZAP
    • 4️⃣4 - Cross-Site Scripting (XSS)
      • 4.1 XSS Anatomy
      • 4.2 Reflected XSS
      • 4.3 Stored XSS
      • 4.4 DOM-Based XSS
      • 4.5 Identifying & Exploiting XSS with XSSer
    • 5️⃣5 - ​SQL Injection (SQLi)
      • 5.1 DB & SQL Introduction
      • 5.2 SQL Injection (SQLi)
      • 5.3 In-Band SQLi
      • 5.4 Blind SQLi
      • 5.5 NoSQL
      • 5.6 SQLMap
      • 5.7 Mitigation Strategies
    • 6️⃣6 - ​Common 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.2 CSRF
      • 6.3 Command Injection
    • 7️⃣7 - ​File & Resource Attacks
      • 7.1 File Upload Vulnerability
      • 7.2 Directory Traversal
      • 7.3 File Inclusion (LFI and RFI)
        • 7.3.1 Local File Inclusion (LFI)
        • 7.3.2 Remote File Inclusion (RFI)
    • 8️⃣8 - CMS Pentesting
      • 8.1 - Wordpress & Drupal
    • 9️⃣9 - Encoding, Filtering & Evasion
      • 9.1 - Obfuscating attacks using encodings
    • 📄Report
      • How to write a PT Report
  • 🛣️RoadMap / Exam Preparation
  • 📔eWPT Cheat Sheet
Powered by GitBook
On this page
  • Session Hijacking
  • Phase 1 - Token Acquisition
  • Phase 2 - Impersonation
  • Impact
  1. eWPTv2
  2. 6 - ​Common 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

Last updated 11 months ago

📝
6️⃣