Skip to content
Noroxi
CVE-2018-21226· NVD / CVE Program· CNA mitre

Certain NETGEAR devices are affected by authentication bypass.

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.70% (FIRST EPSS); higher than 51.8% of all records.
  • 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.
  • 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

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

Follow it and we'll tell you in the daily email digest when the record enters KEV, gets exploit code, is updated (including a fix) or its EPSS rises 20 points in a week. Connect a webhook and KEV listings and weaponized exploits arrive instantly.

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Certain NETGEAR devices are affected by authentication bypass. This affects JNR1010v2 before 1.1.0.48, JWNR2010v5 before 1.1.0.48, WNR1000v4 before 1.1.0.48, WNR2020 before 1.1.0.48, and WNR2050 before 1.1.0.48.

HighCVSS 8.8 · v3.1—No exploit No fix recorded
Published
Apr 28, 2020
Updated
Jun 16, 2026
EPSS
0.7% · 52th percentile

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

CNA vs NVD score

NVD
8.8
CNA · mitre
8.8
agree

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.

Noroxi 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 help

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

VendorProduct
netgearjnr1010 firmware
netgearjnr1010
netgearjwnr2010 firmware
netgearjwnr2010
netgearwnr1000 firmware
netgearwnr1000
netgearwnr2020 firmware
netgearwnr2020
netgearwnr2050 firmware
netgearwnr2050

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.48
  • netgear jwnr2010 firmwarebefore 1.1.0.48
  • netgear wnr1000 firmwarebefore 1.1.0.48
  • netgear wnr2020 firmwarebefore 1.1.0.48
  • netgear wnr2050 firmwarebefore 1.1.0.48

Same product

netgear: all records

Other 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-2017-18749Certain NETGEAR devices are affected by CSRF.
    35Monitor
  • CVE-2016-11057Certain NETGEAR devices are affected by mishandling of repeated URL calls.
    30Monitor
  • CVE-2017-18763Certain NETGEAR devices are affected by incorrect configuration of security settings.
    26Monitor

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

  • 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

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

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

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

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