Pixie Dust Attack WPS with Reaver
In this tutorial we are going to do a pixie dust attack using Reaver 1.5.2, Aircrack-NG and Pixiewps. Pixie Dust attack is an offline attack which exploits a WPS vulnerability. The tool, Pixiewps, is written in C and works with a modified version of Reaver. When a wireless router is vulnerable for this attack retrieving the passphrase can be done in seconds. A link to the list of pixie dust vulnerable routers is included at the bottom of this tutorial.
Pixie Dust Attack
Letās put the wifi interface in monitoring mode using:
airmon-ng start wlan0
If necessary kill the processes Kali is complaining about:
Pixie dust attack Reaver
For anyone getting the following error in Kali Linux 2.0 Sana:
[X] ERROR: Failed to open āwlan0monā for capturing
Try the following as a solution:
1. Put the device in Monitor mode Airmon-ng start wlan0
2. A monitoring interface will be started on wlan0mon
3. Use iwconfig to check if the interface MODE is in managed mode, if so then change it to monitor instead of managed with the following commands:
ifconfig wlan0mon down
iwconfig wlan0mon mode monitor
ifconfig wlan0mon up
4. iwconfig check if the mode is monitoring mode now
5. airodump-ng wlan0mon
Start airodump-ng to get the BSSID, MAC address and channel of our target.
airodump-ng -i wlan0mon
Now pick the target and use the BSSID and the channel for Reaver:
Reaver -i wlan0mon -b [BSSID] -vv -S -c [AP channel]
We need the PKE, PKR, e-hash 1 & e-hash 2, E-nonce / R-nonce and the authkey from Reaver to use for pixiewps.
Pixie dust attack Reaver
Now start pixiewps with the following arguments:
Pixie dust attack Reaver
Components:
āE-Hash1 is a hash in which we brute force the first half of the WPS PIN.
āE-Hash2 is a hash in which we brute force the second half of the WPS PIN.
āHMAC is a function that hashes all the data in parenthesis. The function is HMAC-SHA-256.
āPSK1 is the first half of the routerās WPS PIN (10,000 possibilities)
āPSK2 is the second half of the routerās WPS PIN (1,000 or 10,000 possibilities depending if we want to compute the checksum. We just do 10,000 because it makes no time difference and itās just easier.)
āPKE is the Public Key of the Enrollee (used to verify the legitimacy of a WPS exchange and prevent replays.)
āPKR is the Public Key of the Registrar (used to verify the legitimacy of a WPS exchange and prevent replays.)
This router does not seem to be vulnerable to pixie dust attack.
Avoiding Reaver router lock-out with Pixiedust loop
When using the -P (Pixiedust loop) option, Reaver goes into a loop mode that breaks the WPS protocol by not using M4 message to avoid lockouts. This option can only be used for PixieHash collecting to use with pixiewps.
In this tutorial we are going to do a pixie dust attack using Reaver 1.5.2, Aircrack-NG and Pixiewps. Pixie Dust attack is an offline attack which exploits a WPS vulnerability. The tool, Pixiewps, is written in C and works with a modified version of Reaver. When a wireless router is vulnerable for this attack retrieving the passphrase can be done in seconds. A link to the list of pixie dust vulnerable routers is included at the bottom of this tutorial.
Pixie Dust Attack
Letās put the wifi interface in monitoring mode using:
airmon-ng start wlan0
If necessary kill the processes Kali is complaining about:
Pixie dust attack Reaver
For anyone getting the following error in Kali Linux 2.0 Sana:
[X] ERROR: Failed to open āwlan0monā for capturing
Try the following as a solution:
1. Put the device in Monitor mode Airmon-ng start wlan0
2. A monitoring interface will be started on wlan0mon
3. Use iwconfig to check if the interface MODE is in managed mode, if so then change it to monitor instead of managed with the following commands:
ifconfig wlan0mon down
iwconfig wlan0mon mode monitor
ifconfig wlan0mon up
4. iwconfig check if the mode is monitoring mode now
5. airodump-ng wlan0mon
Start airodump-ng to get the BSSID, MAC address and channel of our target.
airodump-ng -i wlan0mon
Now pick the target and use the BSSID and the channel for Reaver:
Reaver -i wlan0mon -b [BSSID] -vv -S -c [AP channel]
We need the PKE, PKR, e-hash 1 & e-hash 2, E-nonce / R-nonce and the authkey from Reaver to use for pixiewps.
Pixie dust attack Reaver
Now start pixiewps with the following arguments:
Pixie dust attack Reaver
Components:
āE-Hash1 is a hash in which we brute force the first half of the WPS PIN.
āE-Hash2 is a hash in which we brute force the second half of the WPS PIN.
āHMAC is a function that hashes all the data in parenthesis. The function is HMAC-SHA-256.
āPSK1 is the first half of the routerās WPS PIN (10,000 possibilities)
āPSK2 is the second half of the routerās WPS PIN (1,000 or 10,000 possibilities depending if we want to compute the checksum. We just do 10,000 because it makes no time difference and itās just easier.)
āPKE is the Public Key of the Enrollee (used to verify the legitimacy of a WPS exchange and prevent replays.)
āPKR is the Public Key of the Registrar (used to verify the legitimacy of a WPS exchange and prevent replays.)
This router does not seem to be vulnerable to pixie dust attack.
Avoiding Reaver router lock-out with Pixiedust loop
When using the -P (Pixiedust loop) option, Reaver goes into a loop mode that breaks the WPS protocol by not using M4 message to avoid lockouts. This option can only be used for PixieHash collecting to use with pixiewps.