Memory corruption via oversized wireless key
Published Dec 23, 2022 · Updated Apr 15, 2025
Stack overflow in D-Link DIR-882 1.30B06 and DIR-878 1.30B08 allows remote authenticated users to corrupt memory through a crafted wireless key. An oversized Key parameter exceeds the SetWLanRadioSecurity module's stack-backed storage and overwrites adjacent memory. Administrative access to the network management interface is required; public sources do not establish code execution or a specific service failure.
Summary
What happened
Stack overflow in D-Link DIR-882 1.30B06 and DIR-878 1.30B08 allows remote authenticated users to corrupt memory through a crafted wireless key. An oversized Key parameter exceeds the SetWLanRadioSecurity module's stack-backed storage and overwrites adjacent memory. Administrative access to the network management interface is required; public sources do not establish code execution or a specific service failure.
The record
- CVE
- CVE-2022-46569
- Published
- Dec 23, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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.
Weakness, pattern, technique
Public exploit references
- 0dayResearch SetWLanRadioSecurity 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