Local authentication bypass via undisclosed mechanism
Published Apr 20, 2020 · Updated Aug 5, 2024
Authentication bypass in affected NETGEAR router firmware allows local users to gain unauthorized access to device functions. NETGEAR has not disclosed the affected component, request path, or authentication operation that processes input incorrectly. Exploitation requires local access and no prior privileges; the accessible functions and resulting actions remain unspecified.
Summary
What happened
Authentication bypass in affected NETGEAR router firmware allows local users to gain unauthorized access to device functions. NETGEAR has not disclosed the affected component, request path, or authentication operation that processes input incorrectly. Exploitation requires local access and no prior privileges; the accessible functions and resulting actions remain unspecified.
The record
- CVE
- CVE-2017-18850
- Published
- Apr 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1212
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 20, 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.
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