Researchers discover massive Wi-Fi vulnerability affecting multiple access points — AirSnitch lets attackers on the same network intercept data and launch machine-in-the-middle attacks
There's a silent vulnerability lurking underneath the architecture of Wi-Fi networks.
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
You are now subscribed
Your newsletter sign-up was successful
A team of researchers from the University of California, Riverside revealed a series of weaknesses in existing Wi-Fi security, allowing them to intercept data on a network infrastructure that they’ve already connected to, even with client isolation in place.
The group called this vulnerability, AirSnitch, and, according to their paper [PDF], it exploits inherent weaknesses in the networking stack. Since Wi-Fi does not cryptographically link client MAC addresses, Wi-Fi encryption keys, and IP addresses through Layers 1, 2, and 3 of the network stack, an attacker can use this to assume the identity of another device and confuse the network into diverting downlink and uplink traffic through it.
Xin’an Zhou, the lead author on the research, said in an interview, according to Ars Technica, that AirSnitch “breaks worldwide Wi-Fi encryption, and it might have the potential to enable advanced cyberattacks.” He also added, “Advanced attacks can build on our primitives to [perform] cookie stealing, DNS and cache poisoning. Our research physically wiretaps the wire altogether so these sophisticated attacks will work. It’s really a threat to worldwide network security.”
AirSnitch does not break encryption at all, but it challenges the general assumption that encrypted clients cannot attack each other because they’ve been cryptographically isolated.
There are four primary ways that AirSnitch uses to bypass client isolation. The first is by abusing shared keys — since most networks use a single password or a Group Temporal Key (GTK), an attacker can make packets aimed for a specific target and wrap it inside a GTK broadcast frame to make it look like legitimate information meant for everyone. The target would then accept the traffic, thinking that it’s a broadcast packet, allowing the attacker to use that as an initial opening for more complex attacks.
Another attack vector is Gateway Bouncing, where the attacker sends data to an access point that’s addressed to a gateway MAC. When the gateway receives it, it sees that Layer 3 IP header, which is the victim’s IP address, but ignores the Layer 2 destination (which is the gateway itself). It then forwards that to the victim, essentially allowing one client to send data to another client without doing so directly. The other two vulnerabilities include MAC spoofing — the attacker can spoof the MAC of the victim, meaning the gateway will forward all downlink traffic to the attacker, or they could spoof the MAC of backend devices, like the gateway, receiving uplink traffic from the target.
The researchers found that these vulnerabilities exist in five popular home routers — Netgear Nighthawk x6 R8000, Tenda RX2 Pro, D-LINK DIR-3040, TP-Link Archer AXE75, and Asus RT-AX57 — two open-source firmwares — DD-WRT v3.0-r44715 and OpenWrt 24.10 — and across two university enterprise networks. This shows that the issue is not just limited to how manufacturers make and program their routers. Instead, it’s a problem with Wi-Fi itself, where its architecture is vulnerable to attackers who know how to take advantage of its flaws.
While this may sound bad, the researchers pointed out that this type of attack is rather complicated, especially with how complicated modern wireless networks have become. Still, that does not mean that manufacturers and standardization groups should ignore this problem. The group hoped that this revelation would force the industry to come together and create a rigorous set of requirements for client isolation and avoid this flaw in the future.
Follow Tom's Hardware on Google News, or add us as a preferred source, to get our latest news, analysis, & reviews in your feeds.
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.

Jowi Morales is a tech enthusiast with years of experience working in the industry. He’s been writing with several tech publications since 2021, where he’s been interested in tech hardware and consumer electronics.
-
TechieTwo Is this a surprise to anyone with a clue? Wi-Fi is so insecure that it's laughable. :(Reply -
EzzyB Reply
Not as bad as it used to be. With previous encryptions you could break into a WiFi network in anywhere from 10 seconds to 10 hours.TechieTwo said:Is this a surprise to anyone with a clue? Wi-Fi is so insecure that it's laughable. :( -
80251 I can only imagine how secure my amplifier-receiver's WiFi link is, which reminds me, I'd better remember to disable it.Reply -
DS426 Reply
Not a specific CVE vulnerability but more of a conceptual framework of exploit attack paths due to fundamental design and implementation flaws of client isolation through sequential network layers, e.g. client isolation forced at Layer 2 ("Data Link" layer in OSI model) but not at the Layer 3 ("Network" layer) can allow for MitM positioning.Sam Hobbs said:Is this a new vulnerability or a new exploitation of an old vulnerability? -
bill001g Reply
Exactly if you read this they have massive amounts of stuff talking about wifi security. Only when you are far into the document do you see what they are really talking about.DS426 said:Not a specific CVE vulnerability but more of a conceptual framework of exploit attack paths due to fundamental design and implementation flaws of client isolation through sequential network layers, e.g. client isolation forced at Layer 2 ("Data Link" layer in OSI model) but not at the Layer 3 ("Network" layer) can allow for MitM positioning.
They "assume" you somehow have obtained access to the network to begin with. They are not talking about attacking some random network. It would be more they could attack other clients that were connected to the same starbucks network. Even then there are multiple layers of protection between wifi clients.
A lot of what they talk about is no different than if someone were to come into your house and plug into your switch. There are all kinds of DNS/dhcp/ arp poison attacks that can be run.
For corporate users there are many levels of protection in commercial equipment. For home users it is a none issue because nobody is going to attack them in the first place.
This paper is almost like the guys that write about all the abilities to crack things and then assume you have physical access to the pc or you have some quantum computer in your back pocket.