CVE-2017-18749: Certain NETGEAR devices are affected by CSRF.
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Certain NETGEAR devices are affected by CSRF. This affects JNR1010v2 before 1.1.0.44, JR6150 before 1.0.1.10, JWNR2010v5 before 1.1.0.44, R6050 before 1.0.1.10, R6100 before 1.0.1.16, R6220 before 1.1.0.50, R7500 before 1.0.0.112, R7500v2 before 1.0.3.20, R7800 before 1.0.2.36, R9000 before 1.0.2.40, WNDR3700v4 before 1.0.2.88, WNDR3700v5 before 1.1.0.48, WNDR4300 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.44, WNR2000v5 before 1.0.0.58, WNR2020 before 1.1.0.44, and WNR2050 before 1.1.0.44.
- Published
- Apr 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-352
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 8.8
- CNA · mitre
- 8.8
- agree
CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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 | r6050 firmware | cpe:2.3:o:netgear:r6050_firmware |
| netgear | r6050 | cpe:2.3:h:netgear:r6050 |
| netgear | r6100 firmware | cpe:2.3:o:netgear:r6100_firmware |
| netgear | r6100 | cpe:2.3:h:netgear:r6100 |
| netgear | r6220 firmware | cpe:2.3:o:netgear:r6220_firmware |
| netgear | r6220 | cpe:2.3:h:netgear:r6220 |
and 20 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.44
- netgear jr6150 firmwarebefore 1.0.1.10
- netgear jwnr2010 firmwarebefore 1.1.0.44
- netgear r6050 firmwarebefore 1.0.1.10
- netgear r6100 firmwarebefore 1.0.1.16
- netgear r6220 firmwarebefore 1.1.0.50
- netgear r7500 firmwarebefore 1.0.0.112
- netgear r7500 firmwarebefore 1.0.3.20
+11 more rows
- netgear r7800 firmwarebefore 1.0.2.36
- netgear r9000 firmwarebefore 1.0.2.40
- netgear wndr3700 firmwarebefore 1.0.2.88
- netgear wndr3700 firmwarebefore 1.1.0.48
- netgear wndr4300 firmwarebefore 1.0.2.90
- netgear wndr4300 firmwarebefore 1.0.0.48
- netgear wndr4500 firmwarebefore 1.0.0.48
- netgear wnr1000 firmwarebefore 1.1.0.44
- netgear wnr2000 firmwarebefore 1.0.0.58
- netgear wnr2020 firmwarebefore 1.1.0.44
- netgear wnr2050 firmwarebefore 1.1.0.44
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
Published before and after this one in the same product
- ← EarlierCVE-2016-11016Oct 16, 2019 · NETGEAR JNR1010 devices before 1.0.0.32 allow webproc?getpage= XSS.24Monitor
- ← EarlierCVE-2017-18763Apr 22, 2020 · Certain NETGEAR devices are affected by incorrect configuration of security settings.26Monitor
- Later →CVE-2018-21209Apr 28, 2020 · Certain NETGEAR devices are affected by reflected XSS.19Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (0)
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.