Security Analysis and Improvements for IEEE 802.11I

Security Analysis and Improvements for IEEE 802.11I

Security Analysis and Improvements for IEEE 802.11i Changhua He John C Mitchell Electrical Engineering and Computer Science Departments Stanford University, Stanford CA 94305 Abstract authentication. RSNA provides two data confidentiality protocols, called the Temporal Key Integrity Protocol This paper analyzes the IEEE 802.11i wireless (TKIP) and the Counter-mode/CBC-MAC Protocol networking standard with respect to data confidentiality, (CCMP), and the RSNA establishment procedure, integrity, mutual authentication, and availability. Under including 802.1X authentication and key management our threat model, 802.11i appears to provide effective protocols. data confidentiality and integrity when CCMP is used. This paper analyzes security aspects of the 802.11i Furthermore, 802.11i may provide satisfactory mutual specification, considering data confidentiality, integrity, authentication and key management, although there are mutual authentication, and availability. Our analysis some potential implementation oversights that may cause suggests that 802.11i is a well-designed standard for data severe problems. Since the 802.11i design does not confidentiality, integrity, and mutual authentication, emphasize availability, several DoS attacks are possible. promising to improve the security of wireless networks. We review the known DoS attacks on unprotected At the same time, some vexing Denial-of-Service (DoS) management frames and EAP frames, and discuss ways of attacks remain. We review the known DoS attacks and mitigating them in 802.11i. The practicality of a DoS describe appropriate countermeasures. We also describe attack against Michael MIC Failure countermeasure is two new DoS attacks – RSN Information Element (RSN discussed and improvements are proposed. Two new DoS IE) Poisoning and 4-Way Handshake Blocking – and attacks and possible repairs are identified: RSN IE present countermeasures for these. We also analyze the Poisoning and 4-Way Handshake Blocking. Finally some failure-recovery strategy in 802.11i and discuss associated tradeoffs in failure-recovery strategies are discussed and tradeoffs. Finally we outline an improved version of an improved variant of 802.11i is proposed to address all 802.11i that addresses all the vulnerabilities discussed in the discussed vulnerabilities. this paper. In proceeding through the analysis of 802.11i, we describe several implementation considerations and 1 Introduction suggest ways to avoid a range of security problems. Here is a concise list of our primary recommendations: First, CCMP should be used for data confidentiality whenever As Wireless Local Area Networks (WLANs) become possible because WEP and TKIP have inherent more widely deployed, wireless security has become a weaknesses. Second, mutual authentication must be serious concern for an increasing number of organizations implemented carefully to achieve security objectives, as [15, 38]. A summary of relevant literature on wireless elaborated in the next paragraph. Third, several security research appears in the Appendix, including implementation details are important for addressing DoS review of standard definitions and acronyms. Generally, vulnerabilities in the MAC layer. Finally, the efficiency of the security requirements for a WLAN include data failure recovery may be improved by using a modified confidentiality, integrity, mutual authentication, and strategy, subject to certain tradeoffs. availability. Strong mutual authentication may be achieved by a IEEE 802.11i [21], an IEEE standard ratified June 24, combination of mechanisms. First, an appropriate 2004, is designed to provide enhanced security in the Extensible Authentication Protocol (EAP) [9] method, Medium Access Control (MAC) layer for 802.11 such as EAP-TLS [2], should be used to prevent Man-in- networks. The 802.11i specification defines two classes of the-Middle (MitM) attacks. Second, the RADIUS [34] security algorithms: Robust Security Network Association secret and the passphrase for Pre-Shared Key (PSK) (RSNA), and Pre-RSNA. Pre-RSNA security consists of generation should be chosen carefully to defend against Wired Equivalent Privacy (WEP) and 802.11 entity dictionary attacks. Third, if Pre-RSNA and RSNA algorithms are allowed to run simultaneously in a WLAN, predictable or redundant; further, encrypted messages a user should have a chance to manually decide which to may be generated upon the requests from the adversary use prior to opening a connection, and Access Points (APs) itself. In our analysis, we consider whether recorded should impose different privilege policies for each. packets and/or knowledge of the plaintext can be used to Otherwise, an adversary may compromise the security of reveal the encryption key, decrypt complete packets, or the entire system through a Security Level Rollback gather other useful information through traffic analysis Attack. Finally, in order to avoid reflection attacks, no techniques. single device should serve as both the authenticator and the supplicant when executing the 4-Way Handshake Threat 2. Message Injection/Active Eavesdropping under the same Pairwise Master Key (PMK). This An adversary is capable of inserting a message into the restriction is straightforward for standard infrastructure wireless network with moderate equipment, such as a networks, but may have some impact on possible uses of station with a common wireless Network Interface Card 802.11i in combination with ad hoc networks. (NIC) and some relevant software. Although the firmware A number of seemingly minor modifications make of most wireless NICs may limit the interface for 802.11i more robust against DoS attacks. First, 802.11i composing packets to the 802.11 standard, an adversary is can eliminate known DoS attacks on the EAP packets by still able to control any field of a packet using known simply ignoring certain packets. Second, when TKIP is techniques [8]. Hence, it is reasonable to assume that an adopted, the Michael MIC (Message Integrity Code) adversary can generate any chosen packet, modify Failure countermeasure could be implemented with contents of a packet, and completely control the improved TKIP Sequence Counter (TSC) updating and transmission of the packet. If a packet is required to be without re-keying in order to make the DoS attack more authenticated, the adversary may be able to break the data difficult. Third, in the RSN IE confirmation mechanism, integrity algorithm to make a valid packet. The adversary the verification condition should be relaxed to mitigate a can also insert a replayed packet, if there is no replay potential DoS attack. Finally, in the 4-Way Handshake, it protection or the adversary is able to avoid it. Furthermore, is better for a supplicant to re-use the same nonce until by inserting some well-chosen packets, the adversary one instance is completed successfully. might be able to learn more information from the reaction The paper is organized as follows. Section 2 describes of the system through active eavesdropping. threats in wireless networks. Section 3 analyzes the data confidentiality and integrity protocols of 802.11i. Section Threat 3. Message Deletion and Interception 4 analyzes the RSNA establishment procedure and We assume that an adversary is able to do message indicates possible implementation mistakes. Section 5 deletion, which means that an adversary is capable of discusses the practical DoS attacks and proposes an removing a packet from the network before it reaches its improved version of 802.11i. Section 6 concludes the destination. This could be done by interfering with the paper. packet reception process on the receiver’s antenna, for example by causing CRC (Cyclic Redundancy Checksum) errors so that the receiver drops the packet. This process 2 Wireless Threats is similar to ordinary packet errors due to noise, but may be instigated by an adversary. In order to analyze the 802.11i protocol, it is important Message interception means that an adversary is able to characterize the likely capabilities of any adversary. to control a connection completely. In other words, the From the Link Layer of a WLAN, there are three possible adversary can capture a packet before the receiver types of frames: Management Frames, Control Frames, actually receives it, and decide whether to delete the and Data Frames. Any manipulation of these frames that packet or forward it to the receiver. This is more directly or potentially jeopardizes data confidentiality, dangerous than the eavesdropping and message deletion. integrity, mutual authentication, and availability will be Furthermore, it differs from eavesdropping and replaying, considered a threat. In this section, we outline some forms because the receiver does not get the packet before the of attack that we consider and evaluate in our analysis. adversary forwards it. Message interception may seem difficult in wireless LANs because the legitimate receiver Threat 1. Passive Eavesdropping/Traffic Analysis might detect a message as soon as the adversary does so. Due to the characteristics of wireless communication, However, a determined adversary does have some an adversary can easily sniff and store all the traffic in a potential ways to achieve message interception. For WLAN. Even when messages are encrypted, it is example, the adversary can use a directional antenna to important to consider whether an adversary may learn delete a packet on the receiver side, while simultaneously partial or complete information from certain messages. using

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    19 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us