Skip to content
Noroxi
CVE-2017-18791· NVD / CVE Program· CNA mitre

Certain NETGEAR devices are affected by CSRF.

Certain NETGEAR devices are affected by CSRF. This affects R6050/JR6150 before 1.0.1.7, PR2000 before 1.0.0.17, R6220 before 1.1.0.50, WNDR3700v5 before 1.1.0.48, JNR1010v2 before 1.1.0.40, JWNR2010v5 before 1.1.0.40, WNR1000v4 before 1.1.0.40, WNR2020 before 1.1.0.40, WNR2050 before 1.1.0.40, WNR614 before 1.1.0.40, WNR618 before 1.1.0.40, and D7000 before 1.0.1.50.

HighCVSS 8.8 · v3.1—No exploit No fix recorded
Published
Apr 21, 2020
Updated
Jun 16, 2026
EPSS
0.5% · 37th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

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.

Affected systems

VendorProduct
netgearr6050 firmware
netgearr6050
netgearjr6150 firmware
netgearjr6150
netgearpr2000 firmware
netgearpr2000
netgearr6220 firmware
netgearr6220
netgearwndr3700 firmware
netgearwndr3700
netgearjnr1010 firmware
netgearjnr1010

and 14 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • netgear d7000 firmwarebefore 1.0.1.50
  • netgear jnr1010 firmwarebefore 1.1.0.40
  • netgear jr6150 firmwarebefore 1.0.1.7
  • netgear jwnr2010 firmwarebefore 1.1.0.40
  • netgear pr2000 firmwarebefore 1.0.0.17
  • netgear r6050 firmwarebefore 1.0.1.7
  • netgear r6220 firmwarebefore 1.1.0.50
  • netgear wndr3700 firmwarebefore 1.1.0.48
  • netgear wnr1000 firmwarebefore 1.1.0.40
  • netgear wnr2020 firmwarebefore 1.1.0.40
  • netgear wnr2050 firmwarebefore 1.1.0.40
  • netgear wnr614 firmwarebefore 1.1.0.40
  • netgear wnr618 firmwarebefore 1.1.0.40

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.

EPSS, last 120 days

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 researchers

Finders, 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

  • 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

Fixed

ts
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.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; 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

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.

All records