Unspecified impact via pre-authentication buffer overflow
Published Apr 28, 2020 · Updated Aug 5, 2024
Buffer overflow in NETGEAR router and gateway firmware allows remote attackers on an adjacent network to cause unspecified impact. NETGEAR has not published the affected component, input vector, or unsafe copy operation that overruns the destination buffer. No authentication or user interaction is required, but reachability is limited to an adjacent network.
Summary
What happened
Buffer overflow in NETGEAR router and gateway firmware allows remote attackers on an adjacent network to cause unspecified impact. NETGEAR has not published the affected component, input vector, or unsafe copy operation that overruns the destination buffer. No authentication or user interaction is required, but reachability is limited to an adjacent network.
The record
- CVE
- CVE-2018-21218
- Published
- Apr 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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