Unauthenticated code execution via unvalidated format string
Published Jul 21, 2023 · Updated Oct 24, 2024
Format-string injection in ASUS RT-AX56U V2 and RT-AC86U firmware allows remote attackers to execute arbitrary code without authentication. The AiMesh ccm_processREQ_CHANGED_CONFIG function insufficiently validates a value passed to cm_processChangedConfigMsg, enabling attacker-controlled format-string processing. Network access to the affected AiMesh request path is sufficient; exploitation can perform arbitrary router operations or interrupt service.
Summary
What happened
Format-string injection in ASUS RT-AX56U V2 and RT-AC86U firmware allows remote attackers to execute arbitrary code without authentication. The AiMesh ccm_processREQ_CHANGED_CONFIG function insufficiently validates a value passed to cm_processChangedConfigMsg, enabling attacker-controlled format-string processing. Network access to the affected AiMesh request path is sufficient; exploitation can perform arbitrary router operations or interrupt service.
The record
- CVE
- CVE-2023-35087
- Published
- Jul 21, 2023
- Updated
- Oct 24, 2024
- Vendor
- ASUSTeK Computer Inc.
- Product
- RT-AC86U
- Classifications
- CWE-134, CAPEC-135, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2023CVE publishedPublication date reported by the CVE source.
- Oct 24, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0.4_386_51529
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo