Wireless Client Isolation Not Enabled
Devices connected to the same wireless network can communicate directly with each other, so one connected device can scan and attack the others.
| Severity | Low |
| CVSS 3.1 | 3.5 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 5.1 CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-653: Improper Isolation or Compartmentalization |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1557.002 ARP Cache Poisoning, T1557.001 Name Resolution Poisoning and SMB Relay |
| Category | Security Misconfiguration |
Description
Client isolation is not enabled on one or more wireless networks, so devices connected to the same SSID can send traffic directly to one another. The feature, called client isolation, AP isolation or peer-to-peer blocking depending on the vendor, makes the access point or controller drop traffic between wireless clients, so that each client can only communicate with the network beyond it.
Without isolation, an attacker who can join the network, which on a guest network may need no more than the displayed key, can discover the other clients, attack them directly through any services they expose, such as file sharing, remote desktop or web interfaces on users' laptops and phones, and carry out attacks that rely on sharing a network segment, such as ARP spoofing or answering broadcast name resolution requests (LLMNR and NBT-NS), to capture credentials. This matters most on guest and public networks, where users and devices are untrusted, and on corporate networks where laptops have local services enabled. The impact depends on the other clients and requires the attacker to be connected first, which is why it is rated low on its own, but it often provides the starting point for more serious attacks.
The weakness is identified by connecting a test device to the network and confirming that other wireless clients respond to discovery and connection attempts. Isolation applied on each access point does not by itself stop traffic between clients on different access points that share a VLAN, so testing from more than one access point can show partial isolation.
Remediation
Enable client isolation on every SSID where clients have no need to communicate with each other, which includes all guest and public networks:
- Turn on the vendor's client isolation or peer-to-peer blocking setting for the SSID. Where the network spans several access points, also enable the equivalent controller-wide setting, or use private VLANs or access control lists, so that isolation applies between access points too.
- On corporate networks where some peer-to-peer traffic is required, such as wireless printing or screen casting, allow only those specific flows with access control lists rather than leaving clients open to each other.
- Reduce what clients expose by enabling host firewalls on managed devices and disabling unneeded sharing services.
Confirm the fix by connecting two test devices to the network, including on different access points, and confirming that neither can reach the other.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.