- The most dangerous jobs in technology
- Burning Man's open source cell phone system could save the world
- Only 5 (all women) of 135 pass Defcon social engineering test
- Fake antivirus software using ransom threats
- Cisco buys wireless smart grid company
Industry analysis by expert Joanie Wexler, plus links to the day's wireless news headlines
Perhaps it was only a matter of time. But wireless security researchers say they have uncovered a vulnerability in the WPA2 security protocol, which is the strongest form of Wi-Fi encryption and authentication currently standardized and available.
Malicious insiders can exploit the vulnerability, named "Hole 196" by the researcher who discovered it at wireless security company AirTight Networks. The moniker refers to the page of the IEEE 802.11 Standard (Revision, 2007) on which the vulnerability is buried.
10 of the worst moments in network security history
Hole 196 lends itself to man-in-the-middle-style exploits, whereby an internal, authorized Wi-Fi user can decrypt, over the air, the private data of others, inject malicious traffic into the network and compromise other authorized devices using open source software, according to AirTight.
The researcher who discovered Hole 196, Md Sohail Ahmad, AirTight technology manager, intends to demonstrate it at two conferences taking place in Las Vegas next week: Black Hat Arsenal and DEF CON 18.
The Advanced Encryption Standard (AES) derivative on which WPA2 is based has not been cracked and no brute force is required to exploit the vulnerability, Ahmad says. Rather, a stipulation in the standard that allows all clients to receive broadcast traffic from an access point (AP) using a common shared key creates the vulnerability when an authorized user uses the common key in reverse and sends spoofed packets encrypted using the shared group key.
Ahmad explains it this way:
WPA2 uses two types of keys: 1) Pairwise Transient Key (PTK), which is unique to each client, for protecting unicast traffic; and 2) Group Temporal Key (GTK) to protect broadcast data sent to multiple clients in a network. PTKs can detect address spoofing and data forgery. "GTKs do not have this property," according to page 196 of the IEEE 802.11 standard.
These six words comprise the loophole, Ahmad says.
Because a client has the GTK protocol for receiving broadcast traffic, the user of that client device could exploit GTK to create its own broadcast packet. From there, clients will respond to the sending MAC address with their own private key information.
Ahmad says it took about 10 lines of code in open source MadWiFi driver software, freely available on the Internet, and an off-the-shelf client card for him to spoof the MAC address of the AP, pretending to be the gateway for sending out traffic. Clients who receive the message see the client as the gateway and "respond with PTKs", which are private and which the insider can decrypt, Ahmad explains.
From there, "the malicious insider could drop traffic, drop a [denial-of-service] attack, or snoop," Ahmad says.
The ability to exploit the vulnerability is limited to authorized users, AirTight says. Still, year-after-year security studies show that insider security breaches continue to be the biggest source of loss to businesses, whether from disgruntled employees or spies who steal and sell confidential data.
Joanie Wexler is an independent networking technology writer/editor in Silicon Valley.
Comments (16)
WPA2By Jose on July 26, 2010, 10:31 amWell I would say he has not done something new as with Backtrack you have the ability to do this. So really he is only exposing what is already known. Please provide...
Reply | Read entire comment
There IS a fix for Hole 196By mbeckman on July 26, 2010, 11:20 amJoanie, you ask "What can we do about Hole 196?", but then imply that nothing can be done wen you quote Mr. Phanse, the discloser of the attack. This problem was...
Reply | Read entire comment
Some references for readersBy mbeckman on July 26, 2010, 12:01 pmFor anyone wanting to employ IPSec over WiFi, here are some quotes and references explaining how to do it: From SonicWall's tech note "10 Steps to Securing Your...
Reply | Read entire comment
Sending PTKsBy Anonymous on July 26, 2010, 12:56 pmAhmad says "Clients who receive the message see the client as the gateway and "respond with PTKs"". PTKs are never sent, they are derived by both parties; as far...
Reply | Read entire comment
Self Promoting Fear Mongering By Anonymous on July 26, 2010, 1:57 pmThis is not news. It's a layer three issue that relates to joining any network. It has nothing to do with WPA2. It is an issue in hotspots and has been addressed...
Reply | Read entire comment
I think the phrase "respondBy Anon on July 26, 2010, 9:34 pmI think the phrase "respond with PTKs" needs some clarification. When clients receive the spoofed (GTK-encrypted) packets from the insider, they will send all their...
Reply | Read entire comment
View all comments