RT-AX56U V2: Use of Externally-Controlled Format String
CVE-2023-35087 is a critical-severity use of externally-controlled format string vulnerability in RT-AX56U V2 from ASUS, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected RT-AX56U V2 versions: 3.0.0.4.386_50460. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.07% chance of exploitation within 30 days, higher than 65% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of RT-AX56U V2 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ASUS | RT-AX56U V2 | 3.0.0.4.386_50460 | Not stated |
| ASUS | RT-AC86U | 3.0.0.4_386_51529 | Not stated |
| ASUS | Rt-ac86u Firmware | 3.0.0.4_386_51529 | Not stated |
| ASUS | Rt-ax56u V2 Firmware | 3.0.0.4.386_50460 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.org.tw).
Official description
It is identified a format string vulnerability in ASUS RT-AX56U V2 & RT-AC86U. This vulnerability is caused by lacking validation for a specific value when calling cm_processChangedConfigMsg in ccm_processREQ_CHANGED_CONFIG function in AiMesh system. An unauthenticated remote attacker can exploit this vulnerability without privilege to perform remote arbitrary code execution, arbitrary system operation or disrupt service. This issue affects RT-AX56U V2: 3.0.0.4.386_50460; RT-AC86U: 3.0.0.4_386_51529.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Externally-Controlled Format String
The product uses a function that accepts a format string as an argument, but the format string originates from an external source.
How developers prevent this class of flaw
- Choose a language that is not subject to this flaw.
- Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings.
- Run compilers and linkers with high warning levels, since they may detect incorrect usage.
More Use of Externally-Controlled Format String vulnerabilities (CWE-134)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- twcert.org.tw/tw/cp-132-7249-ab2d1-1.htmlThird Party Advisory
Other vulnerabilities in RT-AX56U V2
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
Recent Use of Externally-Controlled Format String vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.