본문으로 건너뛰기
cccskills
무료GitHub에 공개

offensive-wpa3-sae

Assess WPA3 wireless security by reviewing mixed WPA2/WPA3 settings and SAE, its password authentication method. Examine implementation weaknesses, H2E support, and 6 GHz requirements to determine relevant tests and detection signals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

WPA3 / SAE (Simultaneous Authentication of Equals) attack methodology — transition-mode (mixed WPA2/WPA3) downgrade, Dragonblood side-channel attacks (CVE-2019-9494, 9495, 13377, 13456), SAE auth flooding for AP CPU exhaustion, Hash-to-Element (H2E) timing analysis, group downgrade, and 6 GHz / Wi-Fi 6E spec implications (PMF mandatory, no transition mode allowed). Use when target advertises WPA3-SAE or WPA3-Personal/Enterprise, or operates in 6 GHz where WPA3 + PMF are required by spec.

설치 방법 보기

이럴 때 유용합니다

  • Reviewing security settings on WPA3 wireless networks
  • Assessing downgrade risks in mixed WPA2/WPA3 deployments
  • Organizing SAE implementation and H2E checks
  • Planning security assessments for 6 GHz wireless networks

포함된 파일(1)

  • SKILL.md6.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

WPA3 / SAE Attacks

WPA3 fixes the offline-handshake-cracking weakness of WPA2 by replacing the 4-way PSK exchange with SAE (a Dragonfly-derived password-authenticated key exchange). The straightforward offline crack disappears — but transition-mode misconfigurations and the original SAE implementation's side-channel leaks open new paths.

Quick Workflow

  1. Verify the target advertises WPA3 (RSN IE shows AKM SAE = 8)
  2. Check for transition-mode (mixed WPA2 + WPA3) — easiest path
  3. If pure WPA3, fingerprint the AP's hostapd version for Dragonblood applicability
  4. Side-channel timing or cache attacks if reachable
  5. Otherwise, accept that offline cracking isn't viable — pivot to other surfaces

Transition-Mode Downgrade

If the AP advertises both WPA2-PSK and WPA3-SAE (transition mode for mixed-client networks), older clients can be forced onto WPA2:

# Identify transition mode in beacon frames
sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID>
# Encryption column shows WPA2 WPA3 (both)

Steps:

  1. Spoof a beacon advertising only RSN-WPA2 with the same BSSID/SSID
  2. Client roams to your beacon, performs WPA2 4-way handshake
  3. Capture handshake exactly like offensive-wpa2-psk
# Use hostapd-mana or airbase-ng for the WPA2-only AP advertisement
airbase-ng -e CorpWiFi -c 6 -W 1 wlan0mon
# -W 1 enables WPA, configure for WPA2-only RSN element

Why this works: WPA3-SAE clients fall back to WPA2-PSK if the AP only advertises WPA2 — there's no protected downgrade defense in transition mode. WPA3-only mode (no transition) blocks this.

Mitigation defenders use: WPA3-only networks (no WPA2). Wi-Fi 6E (6 GHz) mandates WPA3-only by spec.

Dragonblood (CVE-2019-9494 / 9495 / 13377 / 13456)

Side-channel and downgrade attacks against the SAE Hunting-and-Pecking algorithm in pre-2.10 hostapd / wpa_supplicant.

Cache-Based Side-Channel

The original SAE password-element derivation iterates a variable number of times depending on the password and MAC. Cache hits leak the iteration count.

git clone https://github.com/vanhoefm/dragonblood
cd dragonblood

# Cache-based attack (requires co-located malicious code on target host — limited)
python3 dragontime.py --bssid AA:BB:CC:DD:EE:FF --iface wlan0mon

Timing Side-Channel

The same iteration count leaks via observable timing of the SAE commit phase from outside.

python3 dragontime.py --bssid AA:BB:CC:DD:EE:FF --iface wlan0mon --mode timing

Downgrade to Weak Group

Some implementations accept SAE with the deprecated MODP group 5 if the client requests it. Combined with cache/timing side channels, this enables offline dictionary attack.

python3 dragondrain.py wlan0mon AA:BB:CC:DD:EE:FF

Patched Versions

ImplementationFixed
hostapd / wpa_supplicant2.10 (April 2022)
Apple iOS / macOS2019 patches
WindowsKB-batched 2019-2020
Embedded routersOften unpatched — high hit rate on consumer SOHO

Hash-to-Element (H2E)

WPA3 R2 introduced H2E to replace the iteration-leaky Hunting-and-Pecking. H2E is constant-time. If the AP advertises H2E in the RSNXE element, Dragonblood-class attacks don't apply.

# Wireshark filter
wlan.rsnx.field.h2e

If H2E is present and required (no Hunting-and-Pecking fallback), only the spec is left to attack — abandon SAE attacks and pivot to other surfaces (PMF check, evil-twin via EAP if Enterprise, supply-chain via management frames).

SAE Auth Flooding (DoS)

SAE's commit phase requires the AP to do heavy elliptic-curve work per association attempt. Floods can exhaust CPU on lower-end APs, denying service to legitimate clients.

sudo mdk4 wlan0mon a -a AA:BB:CC:DD:EE:FF -m -s 1024
# Auth attack mode -a, multiple per second -s 1024

This is a DoS — only with explicit authorization. Modern enterprise APs use anti-clogging tokens to throttle SAE-flood attacks; consumer routers often don't.

6 GHz / Wi-Fi 6E Implications

The 6 GHz band (Wi-Fi 6E, channels 1–233 in the 5925–7125 MHz range) requires:

  • WPA3-only (no transition mode)
  • PMF (802.11w) mandatory (deauth/disassoc protected)
  • OWE (Opportunistic Wireless Encryption) for open networks

Net effect: most pre-WPA3 attacks (deauth, transition-mode downgrade) don't apply on 6 GHz. Pure SAE side-channel, evil-twin, or out-of-band attacks remain viable.

Detection Considerations

WPA3 is enterprise-defended much like WPA2 — WIDS catches:

  • Beacon spoofing (transition-mode downgrade) via fingerprint mismatch (IE order, vendor-specific, beacon timing)
  • SAE flood via association rate per source MAC
  • Repeated SAE commit failures (timing attack telemetry)

Successful Dragonblood-class attacks against patched modern hostapd are unlikely. Consumer SOHO and embedded APs are still in scope.

Engagement Cheatsheet

# 1. Identify mode
sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID>
# Encryption: WPA2 + WPA3 → transition; WPA3-only → SAE-only

# 2. Transition-mode downgrade attempt
sudo airbase-ng -e <ESSID> -c <ch> -W 1 -z 4 wlan0mon  # WPA2-RSN advertised only

# 3. Wait for client roam, capture WPA2 handshake (handoff to offensive-wpa2-psk)

# 4. If pure WPA3, fingerprint hostapd
# (passive analysis of beacon IE order + version-specific behaviors)

# 5. Run Dragonblood test scripts if pre-2.10 hostapd suspected
python3 dragondrain.py wlan0mon <BSSID>
python3 dragontime.py --bssid <BSSID> --iface wlan0mon

# 6. Document residual viable attacks; pivot to evil-twin / EAP / RF if pure WPA3 R2

Key References

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Assess Active Directory security by mapping accounts, permissions, and paths to administrative access. The skill covers credential misuse, certificate service misconfigurations, movement between systems, and hybrid identity environments involving Entra ID.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Mapping paths to administrative access in Active Directory
  • Reviewing ADCS certificate service configurations
  • Assessing permissions, delegation, and group policies
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

Organize red team exercises that simulate adversaries to assess an organization's detection and response. Covers engagement rules, infrastructure, operational controls, evidence handling, and reports that help security teams review gaps and prioritize improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Defining red team objectives and engagement rules
  • Designing an exercise that assumes an existing breach
  • Organizing evidence and activity logs
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

Review how evidence can be altered during authorized security exercises on Windows and Linux. Covers logs, timestamps, memory, disk records, and network traces, alongside the signs defenders use to detect manipulation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning authorized evidence manipulation tests
  • Reviewing Windows and Linux forensic artifacts
  • Checking detection coverage for altered evidence
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

Assess API business workflows for flaws that automated scanners can miss. The skill examines skipped steps, simultaneous transactions, authentication tokens, GraphQL, and webhooks, helping testers document weaknesses and their financial or operational impact during authorized assessments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing order and payment workflow integrity
  • Testing concurrent coupon redemption or transfers
  • Assessing JWT validation and GraphQL controls
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

Test REST, gRPC, and WebSocket APIs for weaknesses in authentication, access controls, input handling, and configuration. Provides protocol-specific checks, tool guidance, and detection indicators to help document reproducible findings and severity during authorized assessments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check access controls across users and roles
  • Review token lifecycles and request limits
  • Assess gRPC and WebSocket security
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

Assess Bluetooth Low Energy devices by inspecting exposed data and commands, pairing methods, captured traffic, and companion apps. The skill provides a testing workflow for identifying authentication gaps and weaknesses in device communication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assessing BLE authentication in smart locks
  • Checking data access on fitness trackers
  • Reviewing pairing security
SnailSploit/Claude-Red7.6천2026년 10월 13일 업데이트

SnailSploit의 스킬 모두 보기

이 스킬의 문제 신고