Memory corruption via unchecked apcliKey copy
Published May 10, 2022 · Updated Aug 3, 2024
Stack-based buffer overflow in TOTOLINK N600R 4.3.0cu.7647_B20210106 allows remote attackers to corrupt process memory via a crafted request. The router web component's FUN_0041bac4 handler copies the JSON apcliKey value directly into stack-local storage without checking its length. Unauthenticated network access to cstecgi.cgi is sufficient; the public proof of concept demonstrates the overwrite under emulation, but not code execution.
Summary
What happened
Stack-based buffer overflow in TOTOLINK N600R 4.3.0cu.7647_B20210106 allows remote attackers to corrupt process memory via a crafted request. The router web component's FUN_0041bac4 handler copies the JSON apcliKey value directly into stack-local storage without checking its length. Unauthenticated network access to cstecgi.cgi is sufficient; the public proof of concept demonstrates the overwrite under emulation, but not code execution.
The record
- CVE
- CVE-2022-29395
- Published
- May 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- setWiFiRepeaterConfig apcliKey proof of conceptproof of concept · demonstrated
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