VLAN Hopping Possible
Switch ports can be made to carry traffic for other VLANs, through trunk negotiation or double-tagged frames, letting an attacker bypass the separation VLANs are meant to provide.
| Severity | Medium |
| CVSS 3.1 | 6.1 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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:N/VI:N/VA:N/SC:L/SI:L/SA:N Open in the calculator |
| CWE | CWE-653: Improper Isolation or Compartmentalization |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1599 Network Boundary Bridging |
| Category | Security Misconfiguration |
Description
VLANs separate devices that share switching hardware into different broadcast domains, and organisations often rely on them to keep user, voice, server and management traffic apart. VLAN hopping is the ability of a device on an access port to send traffic into, or receive traffic from, VLANs other than the one assigned to it, so that the separation fails. An attacker connected to an affected user or public network port can then reach VLANs that should be isolated from it, such as server, management, voice or payment networks, and attack the systems on them directly.
The two common forms are switch spoofing and double tagging. In switch spoofing, the attacker's device negotiates a trunk with the switch using Cisco's Dynamic Trunking Protocol (DTP), which is possible when the port is left in a dynamic mode such as dynamic desirable or dynamic auto; the port then carries every permitted VLAN, and the attacker can create virtual interfaces on any of them. With a trunk formed, the attacker can also receive broadcast and flooded traffic from the other VLANs and use attacks that need a local network position, such as ARP spoofing, on them. In double tagging, the attacker sends frames with two 802.1Q tags when their access VLAN is also the native VLAN of a trunk; the first switch removes the outer tag and the next switch forwards the frame on the VLAN named in the inner tag. Double tagging works in one direction only, but lets traffic be sent to systems on the target VLAN. A related weakness is a voice VLAN that admits any device which announces itself as a phone through CDP or LLDP.
The weakness is identified by listening on an access port for DTP, CDP and LLDP frames, and confirmed with tools such as Yersinia, frogger or VoIP Hopper that attempt trunk negotiation or voice VLAN access, or by sending double-tagged frames and checking for their arrival on the target VLAN.
Remediation
- Configure every user-facing port as a static access port and disable trunk negotiation, with
switchport mode accessandswitchport nonegotiate. - On trunk ports, set trunking explicitly with
switchport mode trunkandswitchport nonegotiate, and allow only the VLANs the link needs withswitchport trunk allowed vlan. - Set the native VLAN on trunks to an unused VLAN that is not assigned to any access port, or tag the native VLAN with
vlan dot1q tag nativewhere the platform supports it, and do not use VLAN 1 for user traffic. - Shut down unused ports and place them in an unused, isolated VLAN.
- Protect voice VLANs with 802.1X, or limit what the voice VLAN can reach, rather than trusting CDP or LLDP announcements alone.
Equivalent settings exist on other vendors' switches. Confirm the fix by repeating the DTP and double-tagging tests from user ports and checking that no traffic reaches other VLANs.
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.