Unauthenticated memory corruption via wepauth parameter
Published Dec 30, 2022 · Updated Apr 11, 2025
Stack overflow in Tenda A15 firmware 15.13.07.13 allows remote attackers to corrupt process memory via a crafted wepauth parameter. The /goform/WifiBasicSet handler permits the attacker-controlled value to exceed a stack buffer's capacity. No authentication or user interaction is required; public evidence establishes memory corruption but does not demonstrate code execution.
Summary
What happened
Stack overflow in Tenda A15 firmware 15.13.07.13 allows remote attackers to corrupt process memory via a crafted wepauth parameter. The /goform/WifiBasicSet handler permits the attacker-controlled value to exceed a stack buffer's capacity. No authentication or user interaction is required; public evidence establishes memory corruption but does not demonstrate code execution.
The record
- CVE
- CVE-2022-47115
- Published
- Dec 30, 2022
- Updated
- Apr 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 2025Record 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
- A15 WifiBasicSet wepauth proof of conceptproof of concept · unverified
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