Guest Wireless Network Not Isolated
The guest wireless network can reach internal systems, so anyone given or able to obtain guest access can attack the corporate network.
| Severity | Medium |
| CVSS 3.1 | 5.4 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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 | T1669 Wi-Fi Networks |
| Category | Insecure Design |
Description
The wireless network provided for visitors is not adequately separated from the organisation's internal network. A client connected to the guest network can reach internal address ranges and services, for example file shares, intranet sites, directory services, printers, or the management interfaces of the wireless infrastructure itself. Common causes are a guest SSID bridged to an internal VLAN, routing between the guest and corporate networks without restrictive firewall rules, internal DNS servers handed to guests, and rules that block some internal ranges but not others.
Guest networks are, by design, used by people the organisation does not control: visitors, contractors, staff's personal devices, and anyone who has been told the guest key or can see it displayed in reception or a meeting room. Many are open or protected only by a captive portal, and the signal frequently reaches beyond the building. Anyone able to join can therefore discover and attack internal systems as though they were on the corporate network, without needing corporate credentials, and malware on visitors' devices can reach internal systems too. The impact depends on what is reachable: exposed management interfaces, unauthenticated services or unpatched systems could lead to compromise of internal hosts, and internal DNS can reveal the structure of the network.
The weakness is identified by connecting to the guest network and attempting to reach internal ranges with host discovery and port scanning, and by checking which DNS servers, gateways and routes are provided. Access to any internal service from the guest network, other than one deliberately offered such as a guest printer, shows that isolation is incomplete.
Remediation
Treat the guest network as an untrusted, internet-only network:
- Place guest traffic on a dedicated VLAN or virtual routing instance with no route to internal networks, or tunnel it to a controller or firewall in a DMZ.
- At the firewall, deny all traffic from the guest network to internal and management address ranges, including all RFC 1918 ranges, and allow only the outbound internet traffic guests need. Write the policy as a default deny rather than a list of blocked subnets.
- Give guests public DNS resolvers or a dedicated guest resolver, not internal DNS servers.
- Block guest access to the management interfaces of the wireless controller, access points and other network devices.
- Enable client isolation on the guest SSID, and apply bandwidth limits and acceptable use terms.
- Where guests genuinely need an internal service, such as a printer, publish only that service through a specific firewall rule.
Confirm the fix by connecting to the guest network and scanning internal and management ranges, confirming that nothing internal responds.
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.