Unauthenticated memory corruption via crafted list parameter
Published Mar 18, 2022 · Updated Aug 3, 2024
Stack overflow in Tenda AC6 firmware 15.03.05.09_multi allows remote attackers to corrupt memory through a crafted list parameter. SetVirtualServerCfg places the list value into stack storage, but the public record does not identify the copy operation or omitted bounds check. Network access to the vulnerable handler is required; a crash is consistent with the flaw, while public evidence does not establish code execution.
Summary
What happened
Stack overflow in Tenda AC6 firmware 15.03.05.09_multi allows remote attackers to corrupt memory through a crafted list parameter. SetVirtualServerCfg places the list value into stack storage, but the public record does not identify the copy operation or omitted bounds check. Network access to the vulnerable handler is required; a crash is consistent with the flaw, while public evidence does not establish code execution.
The record
- CVE
- CVE-2022-25450
- Published
- Mar 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 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
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