AI Agent Hub
Back to skills
🔒

Offensive WPA3-SAE

IT Ops & Security Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_3c6cb52e/offensive-wpa3-sae-sh-p3frbj using https://skillhub.cn/install/skillhub.md

About this skill

Problem Context

WPA3 replaces WPA2's 4-way PSK exchange with SAE, so capturing a handshake and cracking it offline is no longer straightforward. In real-world assessments, the attack surface moves to transition-mode downgrade, older hostapd / wpa_supplicant implementations vulnerable to Dragonblood side-channel issues, and resource abuse around the SAE commit phase. This skill organizes those paths into a practical wireless security evaluation workflow.

How It Works

The skill starts by confirming whether the target advertises WPA3: inspect the RSN IE for AKM SAE, then determine whether WPA2-PSK is also offered. If transition-mode is present, an attacker can build a spoofed beacon advertising WPA2 only, coax WPA2-compatible clients into falling back, capture the 4-way handshake, and process the credential material the same way as WPA2-PSK. For pure WPA3 targets, the workflow focuses on fingerprinting the hostapd version and checking whether CVE-2019-9494 / 9495 / 13377 / 13456–related cache, timing, or weak-group issues apply. It also calls out H2E: when an AP uses WPA3 R2's constant-time H2E and does not fall back to Hunting-and-Pecking, Dragonblood-class attacks generally do not apply. The material also covers SAE auth flooding as a DoS vector, 6 GHz / Wi-Fi 6E requirements for WPA3-only and PMF, and detection signals such as beacon spoofing, association rate, and repeated SAE commit failures.

Scope and Caveats

  • Transition-mode downgrade only works when the network advertises both WPA2 and WPA3; WPA3-only networks block that path.
  • Dragonblood-class attacks mainly target unpatched implementations or devices that still expose the old algorithm; consumer SOHO and embedded APs are more likely to be in scope than modern enterprise gear.
  • SAE Auth Flooding is a DoS technique and should only be used with explicit authorization; enterprise APs may use anti-clogging tokens, while lower-end APs may be more susceptible.
  • 6 GHz / Wi-Fi 6E generally enforces WPA3-only and PMF, significantly weakening traditional deauth and transition-mode downgrade paths.

Use Cases

  • During an authorized test, verify whether the target advertises WPA3 and transition-mode to decide if WPA2 fallback capture is possible.
  • Review enterprise Wi-Fi for transition-mode exposure, abnormal SAE commit behavior, or beacon spoofing signs, then draft WIDS rules.
  • Assess consumer SOHO or embedded APs for hostapd versions that may be affected by Dragonblood-related side-channel issues.
  • Analyze how WPA3-only and PMF on 6 GHz / Wi-Fi 6E limit deauth and transition-mode downgrade, then adjust attack and defense plans.

Best For

  • Wireless penetration tester: needs to assess the WPA3/SAE attack surface using RSN IE, transition-mode, and H2E signals.
  • SOC analyst maintaining WIDS: needs to detect beacon spoofing, abnormal SAE commits, and SAE flooding indicators.
  • IT security owner evaluating office or guest Wi-Fi: needs to confirm transition-mode, PMF, and 6 GHz compliance settings.
  • Wireless security researcher analyzing AP firmware: needs to map hostapd versions and Dragonblood/H2E boundaries to exploitable targets.