1/27/02 chapter 16 wireless networks
TRANSCRIPT
1/27/02 Chapter 16 Wireless Networks 1
Wireless Networks - Principle Characteristics
Provide network access without wires – to reduce cost of wiring, support inherently mobile devices – palms, laptops, PDAs.
• Use unconstrained media (e.g., radio) for transmission – no wires• Three major system classes
• Wide Area Networks (WAN) – world–wide (global) in extent• Local Area Networks (LAN) – campus-wide in extent• Personal Area Networks (PAN) – office-wide in extent
• Relatively new technologies –first developed in the mid-80s• Strongly support personal mobility – locally to globally• Many protocols, technologies, and implementations (new)• Standards relatively immature• Many security problems at all levels – theory, standards, implementation
1/27/02 Chapter 16 Wireless Networks 2
Wireless Threats
Denial of Service – radio frequency jamming or message flooding
Interception – eavesdrop since the signals are broadcast over the air
Manipulation – changing messages
Masquerading – posing as a legitimate user to enter a network
Any wireless system should protect against these threats in the basic system design, implementation, and operational environment
Some do well, others are in bad shape!
1/27/02 Chapter 16 Wireless Networks 3
Wireless Networks - Fundamentals
Network
Destination Network Access Point
Wire Transmission Path
Radio Transmission Path
Mobile Devices
Cell Phone
Palm Pilot
Laptop
1/27/02 Chapter 16 Wireless Networks 4
Wireless Wide Area Networks (WAN)
WANWide Area Network(National/Global)
Licensed, 800-900 Mhz, 1.8-1.9 Ghz
• Started with cellular phones (U.S.,1982)
– 1G, 2G, 3G, 4G
• Protocols - many
–AMPS, TDMA, CDMA, GSM, CDPD, GPRS,UMT-2000,…
• Rapid Growth – “By 2002, wireless phones worldwide will outnumber TVs and PCs combined.”
–Strategic News Service
1/27/02 Chapter 16 Wireless Networks 5
Wireless Wide Area Networks (WAN)
• Started with cell phones – many technologies & standards• Progressed through multiple generations
• Analog voice phones• Digital voice phones• Web-enabled phones
• Despite multiple generations, technology is still immature and changing dynamically (e.g., web access from a cell phone)• Many providers – crowded market• Interoperability a mixed bag – some good, some bad• Some very differentiated products (voice-only, data only, mixed)• Don’t expect convergence anytime soon
1/27/02 Chapter 16 Wireless Networks 6
Wireless Devices and Selected Characteristics
Access PointPalm VIIBlackberryDigital PhoneCDPD Modem
WA
N
WirelessDevice
na500500125500
PurchaseCost ($)
From fees240400360480
Network Service($/device-yr)
NetworkBandwidth
(kbps)Key Features
66
1919
carrier ownedno Outllook, coverage
Outlook, coveragevoice, CDPD-WAP
good coverage
1/27/02 Chapter 16 Wireless Networks 7
Blackberry Handheld Devices – Single purpose device
Wireless e-mail using Microsoft Exchange
1/27/02 Chapter 16 Wireless Networks 8
A Specific Service - Blackberry Real-time messaging
Outlook/ExchangeServers
YourOffice
Colleague'sOffice
Internet
1
2 3
4
6
You
Blackberry Network5
1. Colleague sends urgent message to you
2. Sent to Exchangeservers
3. Received at yourdesktop PC (if on)
4. Encrypted and sent through the internet
5. Transmitted by Blackberry network
6. Blackberry receives and decrypts message for you
Firewall
1/27/02 Chapter 16 Wireless Networks 9
Blackberry Architecture
Blackberry Handheld
Wireless Network Access Point
Internet
Firewall
Exchange Server
Blackberry Server
User’s Desktop
1/27/02 Chapter 16 Wireless Networks 10
Blackberry Architecture – How It Works
• Mail arrives at the user’s desktop in the usual way• Blackberry software is installed on the user’s desktop and configured according to user-specified filtering/forwarding rules• Messages to be forwarded are compressed and encrypted and forwarded to the Blackberry enterprise server that maintains an outbound connection to the Blackberry network (through the firewall and Internet)• Messages are forwarded and displayed on the Blackberry handheld
• Similarly, messages can be originated on the handheld, sent back to the user’s desktop and sent out over the mail connection.
• Can operate in two modes • Wireless LAN mode - as described above• Directly between two handheld devices (peer-to-peer)
1/27/02 Chapter 16 Wireless Networks 11
Blackberry Protection
• Peer-to-peer mode is not secure (scrambled, but not encrypted)
• Wireless network mode:• Symmetric encryption with key shared between desktop & handheld• 3 DES encryption method, key exchange while handheld is docked• Server is behind firewall, only supports outbound connections, followed by out-bound/in-bound communications
Secured Path Unsecured Path
Blackberry User’s Desktop Another User
1/27/02 Chapter 16 Wireless Networks 12
WANWide Area Network
(National/Global)
WANWide Area Network
(National/Global)
LANLocal Area Network(Campus/Building)
LANLocal Area Network(Campus/Building)
Unlicensed, 900 Mhz, 2.4 Ghz, 5 Ghz
Local Area Network (LAN)
• IEEE Standards– 802.11, 1998 (2 Mbps)– 802.11b, 1999 (11 Mbps)– 802.11a, 1999 (54 Mbps)
• Interface Prices– $500 – 1997 (2 Mbps)– $160 – 2000 (11 Mbps)
• Wireless Options Today– Laptops - Apple, Dell,
Gateway, IBM, Compaq, Acer…
Wireless Local Area Network (LAN)
1/27/02 Chapter 16 Wireless Networks 13
You
Wireless Access Point
LAN
Lab/Conference Room
YourOffice
Work untethered Improve productivity by
saving time (use idle time, minimize meeting prep time)
Have real-time access for urgent messages and key information
Wireless Local Area Network (LAN)
1/27/02 Chapter 16 Wireless Networks 14
Local Area Networks (LAN)
Function – wireless equivalent to Ethernet Local Area Network
Based on IEEE standard 802.11 series
• 802.11 – 1997, data rates to 2 Mb/s (outdated)• 802.11b - 1999, data rates to 11 Mb/s (available now)• 802.11g - 2000, data rates to 22 Mb/s (available 2002)• 802.11a - emerging, data rates to 54 Mb/s (available late 2001)
802.11b is dominant technology being implemented.
Part of the specification is the Wired Equivalent Protocol (WEP)designed to protect link layer (over-the-air) traffic from eavesdropping and other attacks (in the words of the IEEEspecification).
1/27/02 Chapter 16 Wireless Networks 15
IEEE 802.11 Standard
The standard describes the Medium Access Control (MAC) andPhysical Layer (PHY) specifications. 802.11 is one part of the 802Specification as shown below.
802.2 Logical Link Control
802.1 Bridging
802.3MeduimAccess
802.3Physical
802.4MeduimAccess
802.4Physical
802.5MeduimAccess
802.5Physical
802.6MeduimAccess
802.6Physical
802.9MeduimAccess
802.9Physical
802.11MeduimAccess
802.11Physical
802.12MeduimAccess
802.12Physical
PhysicalLayer
DataLinkLayer
Ethernet Token Bus Token Ring Dual Bus Integrated Wireless Demand Services Priority
1/27/02 Chapter 16 Wireless Networks 16
802.11 Wireless Local Area Network (LAN)
• Three (3) possible physical layers are specified:• Infared (short range – line of sight)• Frequency Hopping Spread spectrum (FHSS)• Direct Sequence Spread Spectrum (DSSS)
• Three frequency bands are used; 900 MHz, 2.4 GHz, and 5 GHz • 802.11b uses DSSS and the 2.4 GHz frequency band• This frequency band is the unregulated Industrial, Scientific, and Medical (ISM) band – possibility for interference. Range is a few 100 - 300 feet – multiple access points provide campus coverage (like cell phones)
• 802.11b data rate is 11 Mb/s, but performance varies as a function of distance between the mobile device and the nearest access point• The specified protocol is Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA)
1/27/02 Chapter 16 Wireless Networks 17
Access Point
Access Point
Wired Network
Wireless Application Servers
Wireless Handheld (WinCE or Palm)
R
To additional Network Segments
High Level Architecture
1/27/02 Chapter 16 Wireless Networks 18
High Level Architecture – Text
Mobile device (Personal Digital Assistant, laptop, Palm Pilot, etc.) requires a radio frequency transmitting/receiving modem and client software compatible with the IEEE standard.
Access point is a bridge between the backside wired network and the frontside wireless network. It transmits and receives wireless protocol frames, does error control, authenticates and authorizes users, encrypts wireless traffic, interfaces to the wired network
Access point
Laptop modem
1/27/02 Chapter 16 Wireless Networks 19
Wired Equivalent Privacy (WEP) – 802.11 security
According to the standard, particular attention was paid to:
• Defeating an adversaries ability to eavesdrop on wireless transmissions in order to preserve confidentiality by encrypting the channel traffic• Providing integrity assurance that a message has not been modified in transit, and• Authenticating users over an encrypted channel
1/27/02 Chapter 16 Wireless Networks 20
Eavesdropping – 802.11 security
• Since transmissions are broadcast over the airwaves, signals can be intercepted. Interception methods are different for each physical layer.
• It has been argued that interception is difficult for infared because of line-of- sight and short distance requirements, Frequency Hopping Spread Spectrum and Direct Sequence Spread Spectrum because of the psuedo-random nature of the signal spreading.
• Reality is that any device designed to receive/transmit 802.11 signals is capable of intercepting all signals from a wireless network.
• It is a simple matter to modify devices drivers and/or flash memory to operate the device in promiscuous mode. Basic assumption – adversaries have access to all signals transmitted between access points and mobile devices!
1/27/02 Chapter 16 Wireless Networks 21
Eavesdropping Encrypted 802.11 Transmissions
Eavesdropping is defeated if the signals are not intelligible – 802.11 encryptstransmissions using RC4 developed in 1987 by Ron Rivest at MIT and is Considered a secure cipher. Reviewing:
• The RC4 algorithm was kept secret for the first 7 years, but was anonymously posted to the Cypherpunks mailing list in 1994 and became public knowledge.
• RC4 is a symmetric cipher and can use several different key lengths. The 802.11 specification allows for 40 bit (export controlled) and longer, typically 128 bit lengths although specific lengths and implementations can vary by vendor. • RC4 is generally considered a strong cipher. The 802.11 implementation operates in Output Feedback (OFB) mode.
1/27/02 Chapter 16 Wireless Networks 22
RC4 – Operated in Output Feedback mode
E E-1
Plaintext pj Plaintext pjCiphertext cj
IV
Key
Ij
Key
Ij
Oj Oj
Leftmostr bits
Leftmostr bits
Oj-1Oj-1
1/27/02 Chapter 16 Wireless Networks 23
RC4 – Text description
The RC4 algorithm has three (3) inputs: a random initialing vector IV, the random secret key k, and the plaintext P
The IV is input to E, the RC4 encryption algorithm along with the key and Eproduces a random keystream that is sent to the output box O.
The output box shifts the keystream out a Byte at a time and each Byte is combined with a Byte of plaintext under the Exclusive OR function.
The output of E (the keystream) is also fed back to the I stage which causesThe keystream to vary as a function of IV and the plaintext.
The process is reversed at the receiver. Both the IV value and the key mustbe known to the receiver.
1/27/02 Chapter 16 Wireless Networks 24
RC4 – more
The secret key is initially distributed to the access point and the mobile device.The method is not specified by the IEEE 802.11 standard, but should be secret.
The IV which changes for each session, is sent in the clear as part of the initial handshake. The IV does not have to be secret since the strength of the algorithm is derived from the algorithm and key, not IV.
However, the integrity of the IV must be a maintained between the transmitter and receiver or the encrytpion/decryption breaks - won’t work. Also, the IV should not be re-used with the same key schedule. Consider 2 messages:
C1 = P1 RC4(IV1, K1) & C2 = P2 RC4(IV1, K1)
C1 C2 = (P1 RC4(IV1, K1)) (P2 RC4(IV1, K1))
That is, the EXOR of 2 ciphertexts will produce the EXOR of the two plaintexts.If one of the plaintexts is known, the second are revealed.
1/27/02 Chapter 16 Wireless Networks 25
Authentication in 802.11
Two basic levels of authentication
Open System Authentication – the default that authenticates any device requesting authentication – essentially “none”
Shared-Key Authentication – The mobile device and the access point mutually authenticate to each other. Three state process:
1. Unauthenticated & unassociated2. Authenticated and unassociated3. Authenticated and associated
Involves passing messages between a mobile station and an access point.
1/27/02 Chapter 16 Wireless Networks 26
Authentication Messages
Initiator (STA) Responder (AP)
Authentication Request – Sequence # 1
Authentication Challenge – Sequence # 2
Authentication Response – Sequence # 3
Authentication Result – Sequence # 4
Challenge is a psuedo-random number, must be re-played by the initiator. If successful, the process is repeated in reverse (i.e., mutual authentication)
1/27/02 Chapter 16 Wireless Networks 27
Integrity Assurance – No change in transit
An integrity checksum is computed for each message exchanged between astation and an access point.
If the checksum computed over the packet does not match the appendedChecksum, the packet is discarded and re-transmission requested.
All of this sounds reasonable on the surface.
Certainly the goals of authentication, integrity, and confidentiality are theappropriate one for protecting the information.
So…how does the standard and its implementation stack up?
TERRIBLE!!!!!!!!!!!
1/27/02 Chapter 16 Wireless Networks 28
The Problems – High level
The authentication exchange reveals the secret key.
It is trivial to mount a known plaintext attack on the network to recover keys
Integrity is not cryptographically assured – messages can be modified withoutbeing readily detected.
Finally, many wireless networks are being operated using open authenticationwithout authentication or encryption. They are optional parts of the standard,not mandatory. Only the weak checksum is mandatory.
So….How do we break such a network?
1/27/02 Chapter 16 Wireless Networks 29
Authentication Breaks
We discussed the 4 message exchange earlier. The break works like this:
1. The first frame is sent in the clear to request authentication – thats Ok.2. The challenge response is returned by the AP – the challenge is not encrypted. The challenge is generated by combining a random number, an IV, and the shared key and is sent in the clear.3. The responding station, extracts the challenge, puts it into a response frame, encrypts it with the shared key using a new IV (sent in the clear) and sends it back.4. The AP decrypts, checks integrity checksum and compares the challenge to the original – if successful, authentication of the station is successful.
An adversary need only capture the clear text challenge and the ciphertext challenge response. Knowing the IV, the attacker can derive the keystream.The adversary can now create a valid response to a new challenge and jointhe network.
1/27/02 Chapter 16 Wireless Networks 30
Encryption Breaks
One of the issues with Output FeedBack (OFB) mode stream encryption is thatencrypting two messages under the same IV and key can reveal informationabout both.
The IV is transmitted in the clear, so it is available. If the IV is a good random number and not re-used, it is protected. Trouble is the IV:
• Is often initialized to 0 in some implementations (no standard requirement)• It is only 24 bits long. If initialized to 0, then it wraps around mod 24.• Doing the math 224 x 2346 B/packet = ~40GB (~320 Gb). • The network has a capacity to do about 432 Gb per day
The adversary can send a message to the network (known plaintext) and sniffthe ciphertext since the network will encrypt it for him (her).
1/27/02 Chapter 16 Wireless Networks 31
Encryption Breaks - contd
Then the adversary sniff the network for another instance of the same IV usedfor the known plaintext message and recovers that ciphertext.
Now the adversary has a known plaintext/ciphertext pair encrypted with thesame secret key and can recover the key.
Since the keys are shared and typically manually distributed, they don’t changevery often.
That in itself is a problem – multiple users with the same key and difficulty inmanually distributing keys tend to influence long time key use
1/27/02 Chapter 16 Wireless Networks 32
Encryption Breaks - Recap
1. Send a plaintext message to a user on the wireless network and sniff the network for the message. Moderate difficulty, trivial with insider help.2. Capture the IV (sent in the clear) and ciphertext.3. Sniff the network for another instance of the same IV with the original message. Not difficult, but may require significant storage space.4. On a hit, the adversary has:a. Original plaintext/ciphertext pair encrypted with the secret key.b. IV and new ciphertext encrypted with the same key.
C1 = P1 RC4(IV1, K1) & C2 = P2 RC4(IV1, K1)
C1 C2 = (P1 RC4(IV1, K1)) (P2 RC4(IV1, K1))
C1, C2, P1, and certainty that the same IV & key were used.
Then C1 C2 P1 = P2
1/27/02 Chapter 16 Wireless Networks 33
Encryption Breaks - Recap
Test: Does C1 C2 P1 = P2?
Assume P1= 0010, P2 = 0100; Keystream for IV, K = 1100
C1 = 0010 1100 = 1110C2 = 0100 1100 = 1000
C1 C2 P1 = 1110 1000 0010 = 0100 --- QED
1/27/02 Chapter 16 Wireless Networks 34
Integrity Assurance
The standard uses the following format:
Message CRC-32
Keystream
=
CiphertextIV
Transmitted Data Stream
1/27/02 Chapter 16 Wireless Networks 35
802.11 Frame Formats
FrameControl
Duration Dest.Address
SourceAddress
BSSIDSeq.No. Frame Body FCS
Frame Control: Version #; Frame type (control,data, management); sub-type; and numerous flags
Duration:
Destination Address:
Source Address:
BSSID:
Sequence Number:
Frame Body:
FCS:
Octets: 2 2 6 6 6 2 0 – 2312 4
1/27/02 Chapter 16 Wireless Networks 36
Improving Wireless Security – IEEE 802.1x
In 802.11 users authenticate to access points and this is subject to the flaws we have already discussed.
IEEE 802.1x describes an authentication method that is much stronger.
Even better, it applies to wired networks as well as wireless networks.
The authentication method is called Extensible Authentication Protocol (EAP)Over LANs (EAP-OL).
It is an extension of EAP that was originally defined for dial-up authenticationUsing the Point-to-Point Protocol PPP (see RFC 2284).
It is also know as port authentication.
1/27/02 Chapter 16 Wireless Networks 37
Wired & Wireless Access Authentication
Consider the following wired and wireless network connections:
HUB
Port
WirelessAccessPoint
(WAP)Port
Wireless Link
Wired Link
Hub: Ethernet hub (or switch) with wired connections to desktop machines.
WAP: Wireless Access Point with wireless connections to wireless-equippedDevices (e.g., laptops, PDAS, etc.).
Authentication:Provided by the port device or by a service called by the portdevice.
1/27/02 Chapter 16 Wireless Networks 38
Wired & Wireless Authentication
In an Ethernet wired network and a Windows environment, a system enters the network at bootup, by sending a request to the local network segment domain controller (found in the system configuration files).
The domain controller prompts the system for authentication credentials (e.g., a username password pair). On success, the system is authenticated.
In an 802.1 wireless network, the system associates with an access point andThe access point authenticates the wireless system and allows/denies entry.
As we have seen, the wireless method is easily defeated.
IEEE 802.1x provides a method to call a stronger authenticator and will work with either a wired or wireless network.
1/27/02 Chapter 16 Wireless Networks 39
IEEE 802.1X Authentication
1
2
3
4
Step 1: Using EAP, the user requests authentication. The Hub or AP forwardsthe request to the AS.Step 2: The AS issues a request for an authenticator (password, token, etc.).Step 3: The user presents the authenticator.Step 4: The AS authenticates or denies the access request and send the resultback to the AP and the user.If authentication succeeds, the AP opens a port for the user. All traffic isencrypted. Session keys are created by the AS and used by the user and AP.
User Hub or Access Point (AP) Authentication Server (AS)
1/27/02 Chapter 16 Wireless Networks 40
IEEE 802.1X Authentication
The Authentication Server is specified in the standard as a RADIUS server.
RADIUS = Remote Authentication Dial-In User Service
RADIUS is the subject of two RFCs, 2138 and 2865.
RFC 2865 is the current RFC and it describes the operations and protocolssupported by a RADIUS server.