Memory corruption via getRegVeriRegister stack overflow
Published Oct 25, 2023 · Updated Sep 11, 2024
Stack overflow in getRegVeriRegister in TP-Link TL-WR886N firmware 7.0_3.0.14_Build_221115_Rel.56908n allows remote attackers to corrupt memory. The public disclosure identifies getRegVeriRegister as the vulnerable locus but does not disclose the input or unsafe operation that overruns its stack buffer. Reachability requires adjacent-network access; no authentication or user interaction is required, and the record does not establish whether exploitation causes a crash or code execution.
Summary
What happened
Stack overflow in getRegVeriRegister in TP-Link TL-WR886N firmware 7.0_3.0.14_Build_221115_Rel.56908n allows remote attackers to corrupt memory. The public disclosure identifies getRegVeriRegister as the vulnerable locus but does not disclose the input or unsafe operation that overruns its stack buffer. Reachability requires adjacent-network access; no authentication or user interaction is required, and the record does not establish whether exploitation causes a crash or code execution.
The record
- CVE
- CVE-2023-46537
- Published
- Oct 25, 2023
- Updated
- Sep 11, 2024
- Vendor
- TP-Link
- Product
- TL-WR886N Firmware
- Classifications
- CWE-787, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Sep 11, 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=7.0_3.0.14_Build_221115_Rel.56908n
What conditions does exploitation require?
What is affected?
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
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