16.05.2014 Views

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Wireless</strong> LAN <strong>Security</strong> 421<br />

with (or without) modification such that the receiving station has no way to tell that the<br />

packet it is receiving is an old (replayed) packet. To see how this attack can be exploited,<br />

consider a hypothetical scenario where Alice is an account holder, Bob is a bank and<br />

Eve is another account holder in the bank. Suppose Alice and Eve do some business and<br />

Alice needs to pay Eve $500. So, Alice connects to Bob over the network and transfers<br />

$500 from her account to Eve. Eve, however, is greedy. She knows Alice is going to<br />

transfer money. So, she captures all data going from Alice to Bob. Even though Eve<br />

does not know what the messages say, she has a pretty good guess that these messages<br />

instruct Bob to transfer $500 from Alice’s account to Eve’s. So, Eve waits a couple of<br />

days and replays these captured messages to Bob. This may have the effect of transferring<br />

another $500 from Alice’s account to Eve’s account unless Bob has some mechanism for<br />

determining that he is being replayed the messages from a previous session.<br />

Replay attacks are usually prevented by linking the integrity protection mechanism to<br />

either timestamps and/or session sequence numbers. However, WEP does not provide for<br />

any such protection.<br />

18.7 Loopholes in 802.11 <strong>Security</strong><br />

To summarize, here is the list of things that are wrong with 802.11 security:<br />

1. 802.11 does not provide any mechanism for key establishment over an unsecure<br />

medium. This means key sharing among STAs in a BSS and sometimes across<br />

BSSs.<br />

2. WEP uses a synchronous stream cipher over a medium, where it is difficult to<br />

ensure synchronization during a complete session.<br />

3. To solve the previous problem, WEP uses a per-packet key by concatenating the<br />

IV directly to the preshared key to produce a key for RC4. This exposes the base<br />

key or master key to attacks like FMS.<br />

4. Since the master key is usually manually configured and static and since the IV<br />

used in 802.11 is just 24 bits long, this results in a very limited key-space.<br />

5. 802.11 specifies that changing the IV with each packet is optional, thus making<br />

key reuse highly probable.<br />

6. The CRC-32 used for message integrity is linear.<br />

www.newnespress.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!