CVE-2021-38514: Certain NETGEAR devices are affected by authentication bypass.
Noroxi assessment
Priority: Monitor (action score 10/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.77% (FIRST EPSS); higher than 55.9% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are 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
Primary sources: NVD · CVE.org · FIRST EPSS
Certain NETGEAR devices are affected by authentication bypass. This affects D3600 before 1.0.0.72, D6000 before 1.0.0.72, D6100 before 1.0.0.63, D6200 before 1.1.00.34, D6220 before 1.0.0.48, D6400 before 1.0.0.86, D7000 before 1.0.1.70, D7000v2 before 1.0.0.52, D7800 before 1.0.1.56, D8500 before 1.0.3.44, DC112A before 1.0.0.42, DGN2200v4 before 1.0.0.108, DGND2200Bv4 before 1.0.0.108, EX2700 before 1.0.1.48, EX3700 before 1.0.0.76, EX3800 before 1.0.0.76, EX6000 before 1.0.0.38, EX6100 before 1.0.2.24, EX6100v2 before 1.0.1.76, EX6120 before 1.0.0.42, EX6130 before 1.0.0.28, EX6150v1 before 1.0.0.42, EX6150v2 before 1.0.1.76, EX6200 before 1.0.3.88, EX6200v2 before 1.0.1.72, EX6400 before 1.0.2.136, EX7000 before 1.0.0.66, EX7300 before 1.0.2.136, EX8000 before 1.0.1.180, RBK50 before 2.1.4.10, RBR50 before 2.1.4.10, RBS50 before 2.1.4.10, RBK40 before 2.1.4.10, RBR40 before 2.1.4.10, RBS40 before 2.1.4.10, RBW30 before 2.2.1.204, PR2000 before 1.0.0.28, R6020 before 1.0.0.38, R6080 before 1.0.0.38, R6050 before 1.0.1.18, JR6150 before 1.0.1.18, R6120 before 1.0.0.46, R6220 before 1.1.0.86, R6250 before 1.0.4.34, R6300v2 before 1.0.4.32, R6400 before 1.0.1.44, R6400v2 before 1.0.2.62, R6700 before 1.0.1.48, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900v2 before 1.2.0.36, R6900 before 1.0.1.48, R7000 before 1.0.9.34, R6900P before 1.3.1.64, R7000P before 1.3.1.64, R7100LG before 1.0.0.48, R7300DST before 1.0.0.70, R7500v2 before 1.0.3.38, R7800 before 1.0.2.52, R7900 before 1.0.3.8, R8000 before 1.0.4.28, R7900P before 1.4.1.30, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, R9000 before 1.0.3.10, RBS40V before 2.2.0.58, RBK50V before 2.2.0.58, WN2000RPTv3 before 1.0.1.32, WN2500RPv2 before 1.0.1.54, WN3000RPv3 before 1.0.2.78, WN3100RPv2 before 1.0.0.66, WNDR3400v3 before 1.0.1.22, WNDR3700v4 before 1.0.2.102, WNDR4300v1 before 1.0.2.104, WNDR4300v2 before 1.0.0.56, WNDR4500v3 before 1.0.0.56, WNR2000v5 (R2000) before 1.0.0.66, WNR2020 before 1.1.0.62, WNR2050 before 1.1.0.62, WNR3500Lv2 before 1.2.0.62, and XR500 before 2.3.2.22.
- Published
- Aug 10, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- —
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- 2.7
- CNA · mitre
- 2.4
- 0.3 point gap
CVSS:3.1/AC:L/AV:A/A:N/C:L/I:N/PR:H/S:U/UI:N
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.
Running WordPress? Scan your site free with WP Lens
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 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 | ex6000 | cpe:2.3:h:netgear:ex6000 |
| netgear | d3600 firmware | cpe:2.3:o:netgear:d3600_firmware |
| netgear | d3600 | cpe:2.3:h:netgear:d3600 |
| netgear | d6000 firmware | cpe:2.3:o:netgear:d6000_firmware |
| netgear | d6000 | cpe:2.3:h:netgear:d6000 |
| netgear | d6100 firmware | cpe:2.3:o:netgear:d6100_firmware |
| netgear | d6100 | cpe:2.3:h:netgear:d6100 |
| netgear | d6200 firmware | cpe:2.3:o:netgear:d6200_firmware |
| netgear | d6200 | cpe:2.3:h:netgear:d6200 |
| netgear | d6220 firmware | cpe:2.3:o:netgear:d6220_firmware |
| netgear | d6220 | cpe:2.3:h:netgear:d6220 |
| netgear | d6400 firmware | cpe:2.3:o:netgear:d6400_firmware |
and 136 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear d3600 firmwarebefore 1.0.0.72
- netgear d6000 firmwarebefore 1.0.0.72
- netgear d6100 firmwarebefore 1.0.0.63
- netgear d6200 firmwarebefore 1.1.00.34
- netgear d6220 firmwarebefore 1.0.0.48
- netgear d6400 firmwarebefore 1.0.0.86
- netgear d7000 firmwarebefore 1.0.1.70
- netgear d7000 firmwarebefore 1.0.0.52
- netgear d7800 firmwarebefore 1.0.1.56
- netgear d8500 firmwarebefore 1.0.3.44
- netgear dc112a firmwarebefore 1.0.0.42
- netgear dgn2200 firmwarebefore 1.0.0.108
- netgear dgnd2200b firmwarebefore 1.0.0.108
- netgear ex2700 firmwarebefore 1.0.1.48
- netgear ex3700 firmwarebefore 1.0.0.76
- netgear ex3800 firmwarebefore 1.0.0.76
- netgear ex6000 firmwarebefore 1.0.0.38
- netgear ex6100 firmwarebefore 1.0.2.24
- netgear ex6100 firmwarebefore 1.0.1.76
- netgear ex6120 firmwarebefore 1.0.0.42
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-35799Certain NETGEAR devices are affected by a stack-based buffer overflow by an unauthenticated attacker.39Monitor
- CVE-2018-21137Certain NETGEAR devices are affected by a hardcoded password.39Monitor
- CVE-2019-20730Certain NETGEAR devices are affected by SQL injection.39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2018-21224Apr 28, 2020 · Certain NETGEAR devices are affected by a buffer overflow by an unauthenticated attacker.35Monitor
- ← EarlierCVE-2020-35787Dec 29, 2020 · Certain NETGEAR devices are affected by a buffer overflow by an authenticated user.32Monitor
- Later →CVE-2021-38525Aug 10, 2021 · Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user.28Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2021-45550137 days apartCertain NETGEAR devices are affected by command injection by an authenticated user.27Monitor
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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.