Script execution via undisclosed stored input
Published Apr 15, 2020 · Updated Aug 5, 2024
Stored cross-site scripting in NETGEAR RBR50, RBS50, and RBK50 before 2.3.5.30 allows local users to inject persistent scripts. NETGEAR has not disclosed the affected management field or endpoint or the precise operation that stores and later renders the input. The accessible data and actions remain undisclosed; NETGEAR's assessment requires high privileges and local access.
Summary
What happened
Stored cross-site scripting in NETGEAR RBR50, RBS50, and RBK50 before 2.3.5.30 allows local users to inject persistent scripts. NETGEAR has not disclosed the affected management field or endpoint or the precise operation that stores and later renders the input. The accessible data and actions remain undisclosed; NETGEAR's assessment requires high privileges and local access.
The record
- CVE
- CVE-2019-20639
- Published
- Apr 15, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 15, 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