Certain NETGEAR devices are affected by incorrect configuration of security settings.
Certain NETGEAR devices are affected by incorrect configuration of security settings. This affects JNR1010v2 before 1.1.0.42, JR6150 before 1.0.1.10, JWNR2010v5 before 1.1.0.42, PR2000 before 1.0.0.18, R6050 before 1.0.1.10, R6120 before 1.0.0.30, R6220 before 1.1.0.50, R6700v2 before 1.2.0.4, R6800 before 1.2.0.4, R6900v2 before 1.2.0.4, WNDR3700v5 before 1.1.0.48, WNR1000v4 before 1.1.0.42, WNR2020 before 1.1.0.42, and WNR2050 before 1.1.0.42.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Apr 22, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 37th percentile
- CWE
- CWE-20
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 6.5
- CNA · mitre
- 8.8
- 2.3 point gap
CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:U/UI:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| netgear | jnr1010 firmware | cpe:2.3:o:netgear:jnr1010_firmware |
| netgear | jnr1010 | cpe:2.3:h:netgear:jnr1010 |
| netgear | jr6150 firmware | cpe:2.3:o:netgear:jr6150_firmware |
| netgear | jr6150 | cpe:2.3:h:netgear:jr6150 |
| netgear | jwnr2010 firmware | cpe:2.3:o:netgear:jwnr2010_firmware |
| netgear | jwnr2010 | cpe:2.3:h:netgear:jwnr2010 |
| netgear | pr2000 firmware | cpe:2.3:o:netgear:pr2000_firmware |
| netgear | pr2000 | cpe:2.3:h:netgear:pr2000 |
| netgear | r6050 firmware | cpe:2.3:o:netgear:r6050_firmware |
| netgear | r6050 | cpe:2.3:h:netgear:r6050 |
| netgear | r6120 firmware | cpe:2.3:o:netgear:r6120_firmware |
| netgear | r6120 | cpe:2.3:h:netgear:r6120 |
and 16 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear jnr1010 firmwarebefore 1.1.0.42
- netgear jr6150 firmwarebefore 1.0.1.10
- netgear jwnr2010 firmwarebefore 1.1.0.42
- netgear pr2000 firmwarebefore 1.0.0.18
- netgear r6050 firmwarebefore 1.0.1.10
- netgear r6120 firmwarebefore 1.0.0.30
- netgear r6220 firmwarebefore 1.1.0.50
- netgear r6700 firmwarebefore 1.2.0.4
- netgear r6800 firmwarebefore 1.2.0.4
- netgear r6900 firmwarebefore 1.2.0.4
- netgear wndr3700 firmwarebefore 1.1.0.48
- netgear wnr1000 firmwarebefore 1.1.0.42
- netgear wnr2020 firmwarebefore 1.1.0.42
- netgear wnr2050 firmwarebefore 1.1.0.42
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-11014NETGEAR JNR1010 devices before 1.0.0.32 have Incorrect Access Control because the ok value of the auth cookie is a special case.40Plan
- CVE-2017-18737Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.36Monitor
- CVE-2017-18734Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.36Monitor
- CVE-2018-21226Certain NETGEAR devices are affected by authentication bypass.35Monitor
- CVE-2017-18749Certain NETGEAR devices are affected by CSRF.35Monitor
- CVE-2016-11057Certain NETGEAR devices are affected by mishandling of repeated URL calls.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.