Protected Management Frames Not Enabled
Wireless networks do not use 802.11w Protected Management Frames, so forged deauthentication frames can disconnect clients at will.
| Severity | Medium |
| CVSS 3.1 | 4.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 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:L/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-306: Missing Authentication for Critical Function |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1498 Network Denial of Service, T1557.004 Evil Twin |
| Category | Security Misconfiguration |
Description
Protected Management Frames (PMF), defined in IEEE 802.11w, are not enabled or not required on one or more wireless networks. Without PMF, management frames such as deauthentication and disassociation frames are not authenticated, so any device in range can forge them using the address of the access point or of a client, and the recipient acts on them.
Tools such as aireplay-ng and mdk4 send forged deauthentication frames to disconnect a single client or every client of an access point, repeatedly if required, so an attacker within range can disconnect chosen clients for as long as they keep sending frames, disrupting wireless users and any devices that depend on the wireless network. More often the technique supports other attacks: forcing clients to reconnect so that their handshakes can be captured for offline cracking of a pre-shared key, or pushing clients off the genuine network towards an evil twin access point. Radio jamming can disrupt any wireless network and PMF does not prevent it, but forged frames are far easier, cheaper and more targeted.
PMF can be disabled, optional (capable) or required. In optional mode, clients that support PMF are protected and older clients are not. PMF is mandatory in WPA3 and optional in WPA2. The setting is identified from the RSN information element in beacons, which shows whether management frame protection is capable or required, and confirmed by sending forged deauthentication frames to a test client.
Remediation
Enable PMF, and require it wherever clients support it:
- Migrate SSIDs to WPA3-Personal or WPA3-Enterprise, which make PMF mandatory. During migration, WPA2/WPA3 transition mode applies PMF to the clients that connect with WPA3.
- On WPA2 networks, set PMF to required where all clients support it, and to optional where some do not. Identify the remaining clients without PMF support from the controller, and plan their upgrade or replacement.
- Enable wireless intrusion detection on the controller to alert on deauthentication floods and on access points broadcasting the organisation's network names.
Confirm the fix by checking that beacons advertise management frame protection as required, and that a test client stays connected when forged deauthentication frames are sent to it.
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.