WPA authentication flaw in ASUS routers enables remote user disconnection

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2021-37910?

CVE-2021-37910 is a vulnerability classified as Improper Control of Interaction Frequency, affecting GT-AXE11000 (affected versions: < 3.0.0.4.386.45898), RT-AX3000 (affected versions: < 3.0.0.4.386.45898), RT-AX55 (affected versions: < 3.0.0.4.386.45898), and 2 more products. This vulnerability is rated Medium, with a CVSS score of 5.3. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

ASUS routers Wi-Fi protected access protocol (WPA2 and WPA3-SAE) has improper control of Interaction frequency vulnerability, an unauthenticated attacker can remotely disconnect other users' connections by sending specially crafted SAE authentication frames.

Affected products and scope

  • ASUS GT-AXE11000: the affected data records unspecified versions less than 3.0.0.4.386.45898 as affected.
  • ASUS RT-AX3000: the affected data records unspecified versions less than 3.0.0.4.386.45898 as affected.
  • ASUS RT-AX55: the affected data records unspecified versions less than 3.0.0.4.386.45898 as affected.
  • ASUS RT-AX58U: the affected data records unspecified versions less than 3.0.0.4.386.45898 as affected.
  • ASUS TUF-AX3000: the affected data records unspecified versions less than 3.0.0.4.386.45898 as affected.

TWCERT lists v3.0.0.4.386.45898 as the update for each named model. This record does not establish the status of other release branches or prove that every later version is unaffected.

Technical details

ASUS routers contain an improper control of interaction frequency weakness, classified as CWE-799, in Wi-Fi authentication using WPA2 and WPA3-SAE. An unauthenticated attacker can send specially crafted SAE authentication frames during authentication and cause another user's connection to be disconnected. The supplied record establishes network reachability and no required user interaction, but it does not state whether the attacker must be within radio range, on the same LAN, or satisfy another placement condition. The implementation details for rate limiting, state handling, and the SAE processing component remain undisclosed.

Exploitability

The vulnerability is remotely reachable over the network, requires no authentication, and requires no user interaction according to the supplied attack attributes. TWCERT characterized the attack as having higher complexity, while the NVD assessment treated the complexity as lower, so the practical conditions affecting reliability or repeatability are not fully settled. The supplied known_exploited and public_exploit fields are null, so the record does not establish active exploitation or the existence of a public exploit. The absence of that information must not be interpreted as evidence that exploitation has not occurred.

Technical impact

  • The confirmed technical outcome is disconnection of another user's connection through specially crafted SAE authentication frames.
  • The primary effect is reduced Wi-Fi availability. The record does not identify an impact to data confidentiality or integrity.
  • Because authentication is not required, an attacker does not need an account on the affected router to target it.
  • The affected client population may include users authenticating to or connected through the vulnerable router, but the number of clients, disruption duration, and ability to interrupt an entire WLAN are not established.
  • The record does not indicate code execution, privilege escalation, or administrative takeover.

Business impact

The flaw can reduce wireless service availability for targeted clients, disrupting access to applications, services, and internal resources that depend on Wi-Fi connectivity. Repeated attacks could cause recurring disconnections for a group of users or a wireless segment, but the achievable scale and duration are not documented. The available evidence describes connection interruption and service disruption, not data disclosure, data modification, or router takeover. The practical effect depends on the deployed model, firmware, and conditions that are not specified in the record.

Remediation

  1. Update each affected model to the model-specific release listed by TWCERT:
  • ASUS GT-AXE11000: v3.0.0.4.386.45898
  • ASUS RT-AX3000: v3.0.0.4.386.45898
  • ASUS RT-AX55: v3.0.0.4.386.45898
  • ASUS RT-AX58U: v3.0.0.4.386.45898
  • ASUS TUF-AX3000: v3.0.0.4.386.45898
  1. After updating, verify the model and installed firmware version on every device. Do not use the update status of one model to infer the status of another model or firmware branch.
  2. If the model or installed version cannot be determined, treat exposure as unknown and perform a model-specific firmware check before marking the device remediated.
  3. The evidence provides no separate mitigation beyond firmware updating. Do not treat an unconfirmed configuration change as a fix.

Detection

  1. Inventory ASUS GT-AXE11000, RT-AX3000, RT-AX55, RT-AX58U, and TUF-AX3000 devices in the managed environment.
  2. Read the actual model and firmware version from the administration interface or device-management inventory, then compare it with the boundaries in affected_summary.
  3. Record whether WPA2 or WPA3-SAE is in use, because the described weakness is in this Wi-Fi authentication protocol.
  4. If the router provides relevant logs, review them for unusual repeated SAE authentication activity together with abrupt client disconnects. Treat this as precautionary monitoring, not as a confirmed indicator.
  5. No specific IOC or log signature is supplied. The absence of matching log events does not prove that a device is safe.
Sources (15)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.