Improper Input Validation Can Crash Certain ASUS Routers

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-2024-11985?

CVE-2024-11985 is a vulnerability classified as Improper Input Validation, affecting RT-AX55 (affected versions: before 3.0.0.4.386_52332), RT-AX55 V2 (affected versions: before 3.0.0.4.386_52332), RT-AX56U (affected versions: before 3.0.0.4.386_51712), and 4 more products. This vulnerability is rated Medium, with a CVSS score of 4.4. Current sources do not report this vulnerability as exploited.

Overview

Original source data

An improper input validation vulnerability leads to device crashes in certain ASUS router models. Refer to the '12/03/2024 ASUS Router Improper Input Validation' section on the ASUS Security Advisory for more information.

Affected products and scope

  • ASUS RT-AX55: default status is unaffected; versions before 3.0.0.4.386_52332 are recorded as affected.
  • ASUS RT-AX55 V2: default status is unaffected; versions before 3.0.0.4.386_52332 are recorded as affected.
  • ASUS RT-AX56U: default status is unaffected; versions before 3.0.0.4.386_51712 are recorded as affected.
  • ASUS RT-AX56U_V2: default status is unaffected; versions before 3.0.0.4.386_52332 are recorded as affected.
  • ASUS RT-AX57: default status is unaffected; versions before 3.0.0.4.386_52332 are recorded as affected.
  • ASUS RT-AX58U: default status is unaffected; versions before 3.0.0.4_388_25127 are recorded as affected.
  • ASUS RT-AX58U V2: default status is unaffected; versions before 3.0.0.4_388_25127 are recorded as affected.

The record does not provide other models or a separate statement covering parallel release branches. Do not infer the status of models or versions that are not listed.

Technical details

The vulnerability is classified as CWE-20 and occurs when router software fails to validate input correctly before processing it. The record confirms device crashes as the impact, but does not identify the input field, endpoint, protocol, processing component, or data form that triggers the failure. The attack vector is network-based and requires high privileges, with no user interaction. Therefore, an actor who already has the required privileged network access could potentially reach the affected processing path, but the specific request sequence remains undisclosed. The affected scope is limited to the ASUS models listed in affected_summary.

Exploitability

  • The vulnerability is reachable over the network and requires high privileges.
  • The recorded attack complexity is high, no user interaction is required, and the security scope remains unchanged.
  • The described outcome is a device crash, affecting availability; the record does not identify an effect on confidentiality or integrity.
  • The supplied record marks public exploit as false and provides no known-exploited designation. This does not prove that exploitation is impossible or has never occurred.

Technical impact

The flaw can crash an ASUS router when a network-accessible actor has sufficient privileges to reach the affected processing path. The primary technical result is loss of device availability, which can interrupt connectivity or administrative functions. The supplied vector does not indicate an effect on confidentiality, integrity, or another security scope. Because the record does not describe the recovery behavior, outage duration and post-crash impact remain unknown. Organisational consequences may include network service interruption and operational support cost, but the record provides no evidence of data compromise or control takeover.

Business impact

  • A crash can interrupt routing, administration, or network connectivity if the device must reboot or requires operator intervention.
  • The resulting outage may increase support workload and affect services that depend on the router.
  • The high-privilege requirement limits the set of actors able to reach the vulnerable path compared with an unauthenticated flaw, but it does not remove risk from compromised or exposed administrative access.
  • The record does not show data disclosure, data modification, privilege escalation, or impact beyond the existing security scope.

Remediation

  1. Identify the exact model and update each device in an affected range to a release outside the corresponding affected boundary through the ASUS update channel for that model. The recorded boundaries are 3.0.0.4.386_52332 for RT-AX55, RT-AX55 V2, RT-AX56U_V2, and RT-AX57; 3.0.0.4.386_51712 for RT-AX56U; and 3.0.0.4_388_25127 for RT-AX58U and RT-AX58U V2.
  2. If an update cannot be applied immediately, temporarily reduce administrative access from untrusted networks and review accounts with high privileges. This is interim exposure reduction based on the recorded attack conditions, not a substitute for an update.
  3. After updating, verify the exact model, software version, and device stability. Do not apply one model's boundary to another model unless ASUS confirms it.
  4. The record does not include a separate solution statement or detailed mitigation instructions; consult the model-specific ASUS update information before deployment.

Detection

  1. Inventory deployed ASUS routers, including their exact model and current software version, with priority for RT-AX55, RT-AX55 V2, RT-AX56U, RT-AX56U_V2, RT-AX57, RT-AX58U, and RT-AX58U V2.
  2. Compare installed versions with each affected boundary in affected_summary; do not infer safe status for models or release branches that are not listed.
  3. Review crash, unexpected reboot, or service interruption events as a precautionary monitoring measure, not as a confirmed IOC.
  4. Check administrative access from external networks and the identities holding high privileges, because the record requires high privileges but does not identify a specific endpoint or log event.
  5. The absence of a crash or suspicious event in available logs does not prove that a device is unaffected.
Sources (9)
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.