You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dominik edited this page Jan 16, 2026
·
1 revision
🟪 SAE Overflow Attack 🟪
Why do you need this?
WPA3 is considered secure, but flawed implementations of the SAE (Dragonfly) handshake can still be abused. This attack targets vulnerable devices by triggering memory handling errors during authentication.
Quick start:
How it works:
Attacker scans for WPA3-SAE enabled networks
Crafted SAE authentication frames are sent to the access point
Vulnerable implementations may mishandle commit/confirm messages
This can lead to crashes, denial of service, or undefined behavior
In some cases, the network becomes temporarily unusable for clients
CLI Workflow:
scan_networks
select_network 1
set_attack sae_overflow
🧠 SAE Overflow is based on implementation flaws, not cryptographic weakness.