simple_wep_crack
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
simple_wep_crack [2007/04/27 18:50] – updated to reflect v.8 darkaudax | simple_wep_crack [2008/12/28 15:39] – Added additional step for injection testing darkaudax | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Tutorial: Simple WEP Crack ====== | ====== Tutorial: Simple WEP Crack ====== | ||
- | Version: 1.03 April 27, 2007\\ | + | Version: 1.09 December 28, 2008\\ |
By: darkAudax | By: darkAudax | ||
- | |||
===== Introduction ===== | ===== Introduction ===== | ||
Line 12: | Line 11: | ||
It is recommended that you experiment with your home wireless access point to get familiar with these ideas and techniques. If you do not own a particular access point, please remember to get permission from the owner prior to playing with it. | It is recommended that you experiment with your home wireless access point to get familiar with these ideas and techniques. If you do not own a particular access point, please remember to get permission from the owner prior to playing with it. | ||
- | I would like to acknowledge and thank the [[http:// | + | I would like to acknowledge and thank the [[http:// |
Please send me any constructive feedback, positive or negative. Additional troubleshooting ideas and tips are especially welcome. | Please send me any constructive feedback, positive or negative. Additional troubleshooting ideas and tips are especially welcome. | ||
- | |||
===== Assumptions ===== | ===== Assumptions ===== | ||
First, this solution assumes: | First, this solution assumes: | ||
- | * You are using drivers patched for injection. | + | * You are using drivers patched for injection. |
- | * You are physically close enough to send and receive access point packets. | + | * You are physically close enough to send and receive access point packets. |
- | * You are using v0.8 of aircrack-ng. If you use a different version then some of the comman options may have to be changed. | + | * There is at least one wired or wireless client connected to the network and they are active. |
+ | * You are using v0.9 of aircrack-ng. If you use a different version then some of the comman options may have to be changed. | ||
Ensure all of the above assumptions are true, otherwise the advice that follows will not work. In the examples below, you will need to change " | Ensure all of the above assumptions are true, otherwise the advice that follows will not work. In the examples below, you will need to change " | ||
- | |||
- | In the examples, the option " | ||
===== Equipment used ===== | ===== Equipment used ===== | ||
Line 39: | Line 36: | ||
You should gather the equivalent information for the network you will be working on. Then just change the values in the examples below to the specific network. | You should gather the equivalent information for the network you will be working on. Then just change the values in the examples below to the specific network. | ||
- | |||
===== Solution ===== | ===== Solution ===== | ||
- | |||
==== Solution Overview ==== | ==== Solution Overview ==== | ||
Line 52: | Line 47: | ||
- Start the wireless interface in monitor mode on the specific AP channel | - Start the wireless interface in monitor mode on the specific AP channel | ||
+ | - Test the injection capability of the wireless device to the AP | ||
- Use aireplay-ng to do a fake authentication with the access point | - Use aireplay-ng to do a fake authentication with the access point | ||
- Start airodump-ng on AP channel with a bssid filter to collect the new unique IVs | - Start airodump-ng on AP channel with a bssid filter to collect the new unique IVs | ||
- Start aireplay-ng in ARP request replay mode to inject packets | - Start aireplay-ng in ARP request replay mode to inject packets | ||
- Run aircrack-ng to crack key using the IVs collected | - Run aircrack-ng to crack key using the IVs collected | ||
- | |||
==== Step 1 - Start the wireless interface in monitor mode on AP channel ==== | ==== Step 1 - Start the wireless interface in monitor mode on AP channel ==== | ||
- | The purpose of this step is to put your card into what is called monitor mode. Monitor mode is mode whereby your card can listen to every packet in the air. Normally your card will only " | + | The purpose of this step is to put your card into what is called monitor mode. Monitor mode is mode whereby your card can listen to every packet in the air. Normally your card will only " |
First stop ath0 by entering: | First stop ath0 by entering: | ||
Line 87: | Line 82: | ||
| | ||
- | Note: In this command we use " | + | Substitute the channel number that your AP runs on for " |
+ | |||
+ | Note: In this command we use " | ||
The system will respond: | The system will respond: | ||
Line 97: | Line 94: | ||
You will notice that " | You will notice that " | ||
- | |||
- | Then enter " | ||
To confirm the interface is properly setup, enter " | To confirm the interface is properly setup, enter " | ||
Line 120: | Line 115: | ||
Tx excessive retries: | Tx excessive retries: | ||
- | In the response above, you can see that ath0 is in monitor mode, on the 2.452GHz frequency which is channel 9 and the Access Point shows the MAC address of your wireless card. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly. | + | In the response above, you can see that ath0 is in monitor mode, on the 2.452GHz frequency which is channel 9 and the Access Point shows the MAC address of your wireless card. Please note that only the madwifi-ng drivers show the MAC address of your wireless card, the other drivers do not do this. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly. |
To match the frequency to the channel, check out: | To match the frequency to the channel, check out: | ||
Line 126: | Line 121: | ||
- | ==== Step 2 - Use aireplay-ng to do a fake authentication with the access point ==== | + | ==== Step 2 - Test Wireless Device Packet Injection |
- | In order for an access point to accept a packet, the source MAC address must already be associated. | + | The purpose of this step ensures that your card is within distance of your AP and can inject |
- | The lack of association with the access point is the single biggest reason why injection fails. | + | Enter: |
+ | |||
+ | | ||
+ | |||
+ | Where: | ||
+ | *-9 means injectin test | ||
+ | *-e teddy is the wireless network name | ||
+ | *-a 00: | ||
+ | *ath0 is the wireless interface name | ||
+ | |||
+ | The system should respond with: | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | The last line is important. | ||
+ | |||
+ | See the [[injection_test|injection test]] for more details. | ||
+ | |||
+ | |||
+ | ==== Step 3 - Start airodump-ng to capture the IVs ==== | ||
+ | |||
+ | The purpose of this step is to capture the IVs generated. | ||
+ | |||
+ | Open another console session to capture the generated IVs. Then enter: | ||
+ | |||
+ | | ||
+ | |||
+ | Where: | ||
+ | *-c 9 is the channel for the wireless network | ||
+ | *-'''' | ||
+ | *-w capture is file name prefix for the file which will contain the IVs. | ||
+ | *ath0 is the interface name. | ||
+ | |||
+ | While the injection is taking place (later), the screen will look similar to this: | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | |||
+ | ==== Step 4 - Use aireplay-ng to do a fake authentication with the access point ==== | ||
+ | |||
+ | In order for an access point to accept a packet, the source MAC address must already be associated. | ||
+ | |||
+ | The lack of association with the access point is the single biggest reason why injection fails. | ||
To associate with an access point, use fake authentication: | To associate with an access point, use fake authentication: | ||
Line 155: | Line 208: | ||
Where: | Where: | ||
- | * 6000 - Reauthenticate | + | * 6000 - Reauthenticate |
* -o 1 - Send only one set of packets at a time. Default is multiple and this confuses some APs. | * -o 1 - Send only one set of packets at a time. Default is multiple and this confuses some APs. | ||
* -q 10 - Send keep alive packets every 10 seconds. | * -q 10 - Send keep alive packets every 10 seconds. | ||
Line 185: | Line 238: | ||
=== Troubleshooting Tips === | === Troubleshooting Tips === | ||
- | *Some access points are configure | + | *Some access points are configured |
+ | |||
+ | Run: tcpdump -n -vvv -s0 -e -i < | ||
+ | |||
+ | You would then look for error messages. | ||
*If at any time you wish to confirm you are properly associated is to use tcpdump and look at the packets. | *If at any time you wish to confirm you are properly associated is to use tcpdump and look at the packets. | ||
Line 197: | Line 254: | ||
Notice that the access point (00: | Notice that the access point (00: | ||
- | If you want to select only the DeAuth packets with tcpdump then you can use: " | + | If you want to select only the DeAuth packets with tcpdump then you can use: " |
+ | ==== Step 5 - Start aireplay-ng in ARP request replay mode ==== | ||
- | ==== Step 3 - Start airodump-ng to capture the IVs ==== | + | The purpose of this step is to start aireplay-ng in a mode which listens for ARP requests then reinjects them back into the network. |
- | + | ||
- | The purpose of this step is to capture the IVs generated. | + | |
- | + | ||
- | Open another console session to capture the generated IVs. Then enter: | + | |
- | + | ||
- | | + | |
- | + | ||
- | Where: | + | |
- | *-c 9 is the channel for the wireless network | + | |
- | *- -bssid 00: | + | |
- | *- -ivs specfifies that you only want to capture the IVs. This keeps the file as small as possible. | + | |
- | *-w capture is file name prefix for the file which will contain the IVs. | + | |
- | *ath0 is the interface name. | + | |
- | + | ||
- | While the injection is taking place (later), the screen will look similar to this: | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | + | ||
- | ==== Step 4 - Start aireplay-ng in ARP request replay mode ==== | + | |
- | + | ||
- | The purpose of this step is to start aireplay-ng in a mode which listens for ARP requests then reinjects them back into the network. | + | |
Open another console session and enter: | Open another console session and enter: | ||
Line 236: | Line 264: | ||
| | ||
- | It will start listening for ARP requests and when it hears one, aireplay-ng will immediately start to inject it. On your home network, here is an easy way to generate an ARP request: | + | It will start listening for ARP requests and when it hears one, aireplay-ng will immediately start to inject it. On your home network, here is an easy way to generate an ARP request: |
Here is what the screen looks like when ARP requests are being injected: | Here is what the screen looks like when ARP requests are being injected: | ||
Line 244: | Line 272: | ||
Read 629399 packets (got 316283 ARP requests), sent 210955 packets... | Read 629399 packets (got 316283 ARP requests), sent 210955 packets... | ||
- | You can confirm that you are injecting by checking your airodump-ng screen. | + | You can confirm that you are injecting by checking your airodump-ng screen. |
- | ==== Step 5 - Run aircrack-ng to obtain the WEP key ==== | + | === Troubleshooting Tips === |
+ | |||
+ | * If you receive a message similar to "Got a deauth/ | ||
+ | |||
+ | ==== Step 6 - Run aircrack-ng to obtain the WEP key ==== | ||
The purpose of this step is to obtain the WEP key from the IVs gathered in the previous steps. | The purpose of this step is to obtain the WEP key from the IVs gathered in the previous steps. | ||
Note: For learning purposes, you should use a 64 bit WEP key on your AP to speed up the cracking process. | Note: For learning purposes, you should use a 64 bit WEP key on your AP to speed up the cracking process. | ||
+ | |||
+ | Two methods will be shown. | ||
Start another console session and enter: | Start another console session and enter: | ||
- | | + | |
Where: | Where: | ||
+ | * -z invokes the PTW WEP-cracking method. | ||
* -b 00: | * -b 00: | ||
- | * output*.ivs selects all files starting with " | + | * output*.cap selects all files starting with " |
+ | |||
+ | To also use the FMS/KoreK method, start another console session and enter: | ||
+ | |||
+ | | ||
+ | |||
+ | Where: | ||
+ | * -b 00: | ||
+ | * output*.cap selects all files starting with " | ||
+ | |||
+ | If you are using 1.0-rc1, add the option " | ||
- | You can run this while generating packets. | + | You can run this while generating packets. |
Here is what success looks like: | Here is what success looks like: | ||
- | Aircrack-ng 0.8 | + | Aircrack-ng 0.9 |
Line 279: | Line 324: | ||
Probability: | Probability: | ||
- | Notice that in this case it took far less then the estimated 250,000 IVs to crack the key. | + | Notice that in this case it took far less then the estimated 250,000 IVs to crack the key. (For this example, the FMS/KoreK attack was used.) |
- | ===== General | + | ===== General |
* Be sure to read all the documentation on the Wiki for the various commands used in this tutorial. | * Be sure to read all the documentation on the Wiki for the various commands used in this tutorial. | ||
* See [[i_am_injecting_but_the_ivs_don_t_increase|Tutorial: | * See [[i_am_injecting_but_the_ivs_don_t_increase|Tutorial: | ||
simple_wep_crack.txt · Last modified: 2018/03/11 20:13 by mister_x