Wi-Fi Security

ESP32 Wi-Fi Security Features

• Support for Protected Management Frames (PMF)

• Support for WPA3-Personal

In addition to traditional security methods (WEP/WPA-TKIP/WPA2-CCMP), ESP32 Wi-Fi supports state-of-the-art security protocols, namely Protected Management Frames based on 802.11w standard and Wi-Fi Protected Access 3 (WPA3-Personal). Together, PMF and WPA3 provide better privacy and robustness against known attacks on traditional modes.

Protected Management Frames (PMF)

Introduction

In Wi-Fi, management frames such as beacons, probes, (de)authentication, (dis)association are used by non-AP stations to scan and connect to an AP. Unlike data frames, these frames are sent unencrypted. An attacker can use eavesdropping and packet injection to send spoofed (de)authentication/(dis)association frames at the right time, leading to the following attacks in case of unprotected management frame exchanges.

• DOS attack on one or all clients in the range of the attacker.

• Tearing down existing association on AP side by sending association request.

• Forcing a client to perform 4-way handshake again in case PSK is compromised in order to get PTK.

• Getting SSID of hidden network from association request.

• Launching man-in-the-middle attack by forcing clients to deauth from legitimate AP and associating to a rogue one.

PMF provides protection against these attacks by encrypting unicast management frames and providing integrity checks for broadcast management frames. These include deauthentication, disassociation and robust management frames. It also provides Secure Association (SA) teardown mechanism to prevent spoofed association/authentication frames from disconnecting already connected clients.

API & Usage

esp_wifi_set_config() can be used to configure PMF mode by setting appropriate flags in pmf_cfg parameter. Currently, PMF is supported only in Station mode. While setting up a Station, configure PMF using two flags capable and required like below.

wifi_config_t wifi_config = {
    .sta = {
         .ssid = EXAMPLE_WIFI_SSID,
         .password = EXAMPLE_WIFI_PASSWORD,
         .pmf_cfg = {
            .capable = true,
            .required = false
         }
    }
};

ESP32 supports three modes of PMF by combination of these two flags -

• PMF Optional : .capable = true, .required = false

• PMF Required : .capable = true, .required = true

• PMF Disabled : .capable = false, .required = false

Depending on what AP side PMF Mode is, the resulting connnection will behave differently. The table below summarises all possible outcomes -

STA Setting	AP Setting	Outcome
PMF Optional	PMF Optional/Required	Mgmt Frames Protected
PMF Optional	PMF Disabled	Mgmt Frames Not Protected
PMF Required	PMF Optional/Required	Mgmt Frames Protected
PMF Required	PMF Disabled	STA refuses Connection
PMF Disabled	PMF Optional/Disabled	Mgmt Frames Not Protected
PMF Disabled	PMF Required	AP refuses Connection

PMF Optional Mode, which is shown in the example of wifi_confit_t, is suggested to be used in all Station configurations. This is to take the additional security benefit of PMF whenever possible without breaking connections with legacy AP’s.

WPA3-Personal

Introduction

Wi-Fi Protected Access-3 (WPA3) is a set of enhancements to Wi-Fi access security intended to replace the current WPA2 standard. It includes new features and capabilities that offer significantly better protection against different types of attacks. It improves upon WPA2-Personal in following ways:

• WPA3 uses Simultaneous Authentication of Equals (SAE), which is password-authenticated key agreement method based on Diffie-Hellman key exchange. Unlike WPA2, the technology is resistant to offline-dictionary attack, where the attacker attempts to determine shared password based on captured 4-way handshake without any further network interaction.

• Disallows outdated protocols such as TKIP, which is susceptible to simple attacks like MIC key recovery attack.

• Mandates Protected Management Frames (PMF), which provides protection for unicast and multicast robust management frames which include Disassoc and Deauth frames. This means that the attacker cannot disrupt an established WPA3 session by sending forged Assoc frames to the AP or Deauth/Disassoc frames to the Station.

• Provides forward secrecy, which means the captured data cannot be decrypted even if password is compromised after data transmission.

Please refer to Security section of Wi-Fi Alliance’s official website for further details.

Setting up WPA3 with ESP32

In IDF Menuconfig under Wi-Fi component, a config option “Enable WPA3-Personal” is provided to Enable/Disable WPA3. By default it is kept enabled, if disabled ESP32 will not be able to establish a WPA3 connection. Currently, WPA3 is supported only in the Station mode. Additionally, since PMF is mandated by WPA3 protocol, PMF Mode should be set to either Optional or Required while setting WiFi config.

Refer to Protected Management Frames (PMF) on how to set this mode.

After these settings are done, Station is ready to use WPA3-Personal. Application developers need not worry about the underlying security mode of the AP. WPA3-Personal is now the highest supported protocol in terms of security, so it will be automatically selected for the connection whenever available. For example, if an AP is configured to be in WPA3 Transition Mode, where it will advertise as both WPA2 and WPA3 capable, Station will choose WPA3 for the connection with above settings. Note that Wi-Fi stack size requirement will increase 3kB when WPA3 is used.

提供有关此文档的反馈