Unauthenticated unspecified impact
Published Nov 22, 2022 · Updated Apr 29, 2025
Buffer overflow in D-Link DIR-882 firmware 1.10B02 and 1.20B06 allows remote attackers to cause unspecified impact via network requests. Published CVE and vendor materials do not identify the affected component, attacker-controlled input, or erroneous buffer operation. No authentication or user interaction is required, but the documented consequence remains unspecified.
Summary
What happened
Buffer overflow in D-Link DIR-882 firmware 1.10B02 and 1.20B06 allows remote attackers to cause unspecified impact via network requests. Published CVE and vendor materials do not identify the affected component, attacker-controlled input, or erroneous buffer operation. No authentication or user interaction is required, but the documented consequence remains unspecified.
The record
- CVE
- CVE-2022-44806
- Published
- Nov 22, 2022
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 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
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