Wireless Testing Methodology
special driver setup
wlan
-
captive portals
- check if you see other MAC addresses and if they work
- check if there is client separation (prior to authentication)
-
what are you expected to do?
- assessment of a wireless networK?
- WPA2 PSK
- WPA2 Enterprise
-
what to do
- evalutate strength of PSK
- review nearby networks
- assessing guest network
- chekcing network access
-
wpa-ps2-exploit
introduction posts to read:
-
- uses hostapd-wpe
-
https://github.com/FluxionNetwork/fluxion
- rogue ap attack
-
https://github.com/derv82/wifite2
- attack WIFI techniques, not fake AP
EAPHammer Posts
- https://medium.com/@s0lst1c3
- https://github.com/s0lst1c3/s0lst1c3.github.io/blob/master/workshops/advanced-wireless-attacks/index.md
- https://github.com/s0lst1c3/eaphammer/wiki/VI.-Attacking-802.11n-Networks
- https://github.com/s0lst1c3/eaphammer/wiki
notes
- rogue AP to install implants
- evil twin to attack wpa/2 eap/psk networks
initial attacks
attacking active probing
Also known as Karma/Mana style attacks. Karma-style attacks are not supported by eaphammer anymore.
More or less the AP will answer to any incoming AP connection request.
use managment frame ACLs for more targeted attacks
--mac-whitelist
, --mac-blacklist
, --ssid-whitelist
, --ssid-blacklist
attacking WPA3/OWE
- opportunistic wireless encryption
- authentication vs. encryption → this is why we have open wireless networks still
- OWE adds encryption (through DH) to open networks
- OWE transition mode: 2 networks, 1 visible open network with link to OWE network in broadcast parameters, one hidden OWE network
- OWE only helps against passive sniffing attacks, not against evil-twin attacks (as there is no authentication)
eap attacks
hostile captive portal
PMKID attack
essid stripping
802.11n
--hw-mode n
, together with --channel-width 20/40
. Channel bonding will automatically used if channel width=40, otherwise can be configured through --th40 plus/minus/auto
other tools
- airmaggedon
- eaphammer