New AirSnitch attack breaks Wi-Fi encryption in homes, offices, and enterprises

Re:New AirSnitch attack breaks Wi-Fi encryption in homes, of... by Chihuahua0633 on Thursday February 26, 2026 @01:05PM (#47169658)

Adding exceptions for certain protocols, IP ranges (maybe multicast, even) are certainly ways around this, but I imagine with every hole you poke to allow something, you are also opening a hole for data to leak.

[ Parent | on HN ]

Re:New AirSnitch attack breaks Wi-Fi encryption in homes, of... by c0nsumer on Thursday February 26, 2026 @01:08PM (#47169694)

Client isolation is done at L2. You can't add exceptions for IP ranges / protocols / etc this way because that's up the stack. Even if devices can learn about each other in other ways, isolation gets in the way of direct communication between them.

[ Parent | on HN ]

Re:New AirSnitch attack breaks Wi-Fi encryption in homes, of... by oasisbob on Thursday February 26, 2026 @01:12PM (#47169763)

The paper makes the point that you need to consider L3 in client isolation too - they call this the gateway bouncing attack. If you can hairpin traffic for clients at L3, it doesn't matter what preventions you have at L2

[ Parent | on HN ]