📕
Blog
  • 🐞Vulnerabilities & Techniques
    • Web Vulnerabilities
      • Open Redirect
      • HTTP Parameter Pollution (HPP)
      • Host Header Injection (HHI)
      • XSS
      • HTML-Injection
      • clickjacking
      • S3
      • EXternal Xml Entity (XXE)
      • XSS prevention | CSP
      • DOM-XSS
      • SQL Injection | SQLI
      • Response Manipulation Technique & How Burp Suite Works
    • API Vulnerabilities
      • Mass Assignment Vulnerability
  • 🚩CTF
    • ASCWG
  • ✍️Writeups
    • Read Writeups
      • REST API WriteUps
      • Web Vulnerabilities WriteUps
    • Technical Writeups
      • Reset Password Poisoning Via Host Header Injection Lead to (ATO)
      • OTP/2FA Bypasses
        • OTP bypasses
  • 😈TryHackMe
    • THM Advent of Cyber 3 (2021) NoSQL WriteUp
  • 🔱Web-CyberTalents
    • CyberTalents-Web-Easy
    • CyberTalents-Web-Medium
    • CyberTalents-Web-Hard
  • 🖇️Pentesting & Bug Hunting Tips
    • ATO Via Host Header Injection
    • OTP Bypass
    • OutLook Plugin Pentest Guide
  • 💻Port-Swigger Labs
    • XML external entity (XXE) injection
    • DOM-XSS
      • DOM XSS in the document.write sink using source location.search
      • Lab: DOM XSS in document.write sink using source location.search inside a select element
      • Lab: DOM XSS in innerHTML sink using source location.search
      • Lab: DOM XSS in jQuery anchor href attribute sink using location.search source
      • Lab: Reflected DOM XSS
      • Lab: Stored DOM XSS
    • SQL injection
      • Lab: SQL injection vulnerability in WHERE clause allowing retrieval of hidden data
      • Lab: SQL injection vulnerability allowing login bypass
      • Lab: SQL injection UNION attack, determining the number of columns returned by the query
      • Lab: SQL injection UNION attack, finding a column containing text
      • Lab: SQL injection UNION attack, retrieving data from other tables
      • Lab: SQL injection UNION attack, retrieving multiple values in a single column
      • Lab: SQL injection attack, querying the database type and version on Oracle
      • Lab: SQL injection attack, querying the database type and version on MySQL and Microsoft
      • Lab: SQL injection attack, listing the database contents on non-Oracle databases
  • 🛜Wireless Networks Penetration Testing
  • ⚔️Wi-Fi Attacks
    • 🕸️Network Scanning attack
    • 🌊DOS / Flooding
      • 1️⃣DoS - Frame Flooding (Deauth, EAPOL, Beacons)
      • 2️⃣DoS- Exploiting Countermeasures (MIC failure)
    • Jamming Attacks (هجمات التشويش)
    • Probe Requests Attack
    • Handshake Attacks
      • Dictionary Attack
      • Clientless Attack
      • KRACK Attack
      • Downgrad Attack
    • Rouge AP Attack
  • Lab Notes
  • RFID and NFC
  • Bluetooth
  • ZigBee
  • Google Map Test
Powered by GitBook
On this page
  1. Wi-Fi Attacks
  2. Handshake Attacks

Clientless Attack

PreviousDictionary AttackNextKRACK Attack

Last updated 11 months ago

  1. PMKID (Pairwise Master Key Identifier) handshake attacks are a specific type of attack targeting WiFi networks that use WPA/WPA2-PSK (Pre-Shared Key) security protocols. PMKID is part of the process for establishing a secure connection between a client device and an access point (AP).

  1. Overview of PMKID Handshake:

    1. Purpose: PMKID is used in WPA/WPA2-PSK to derive the Pairwise Transient Key (PTK) for securing communications between a client device and an AP.

    2. PMKID Generation:

      • When a client attempts to connect to an AP using a pre-shared key (PSK), the AP sends a PMKID to the client after successful authentication.

      • The client then verifies the PMKID with its own calculation to ensure both devices derive the same PTK for encryption.

    PMKID Handshake Attack:

    1. Attack Method:

      • Capture PMKID: An attacker captures the PMKID during the initial connection attempt between a client and an AP. This can be achieved passively by sniffing WiFi traffic.

    2. Tools Used: Attackers often use tools such as hcxdumptool, hcxpcaptool, or hashcat to capture and process PMKID information.

    3. Objective: The primary objective of capturing PMKID is to launch offline brute-force attacks against the PSK to recover the WiFi network’s passphrase.

    4. Brute-Force Attack:

      • Once the PMKID is captured, attackers use powerful computing resources and password-cracking techniques to guess the PSK through brute-force or dictionary attacks.

      • This process involves trying multiple combinations of passwords until the correct one is found that matches the PMKID.

    Mitigation Strategies:

    To defend against PMKID handshake attacks, consider implementing these mitigation strategies:

    • Use Strong and Complex PSKs: Choose a PSK that is long, random, and difficult to guess or crack.

    • Enable WPA3: Transition to WPA3 if supported, as it provides enhanced security features and mitigates vulnerabilities associated with WPA/WPA2-PSK.

    • Monitor WiFi Traffic: Continuously monitor WiFi networks for unusual activity or unauthorized devices capturing PMKIDs.

    • Update Firmware: Keep APs and client devices updated with the latest firmware to patch known vulnerabilities.

    • Intrusion Detection Systems (IDS): Deploy IDS to detect and alert on suspicious activities related to PMKID capture attempts.

    • Network Segmentation: Segment networks and apply access controls to limit the impact of compromised devices.

    By implementing these measures, organizations can strengthen their defenses against PMKID handshake attacks and enhance the overall security of their WiFi networks.

⚔️