dbcve.org
R6400 FirmwareOperating system · Netgear

CVE-2021-38515

HIGH · 7.5 CVSS v3.1 Published 2021-08-11
Fix available
A fix is available. Upgrade to 1.0.3.18 / 1.0.4.46 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain NETGEAR devices are affected by denial of service. This affects R6400v2 before 1.0.4.98, R6700v3 before 1.0.4.98, R7900 before 1.0.3.18, and R8000 before 1.0.4.46.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A denial of service vulnerability exists in multiple NETGEAR router models (R6400v2, R6700v3, R7900, R8000). The vulnerability can be exploited to cause service disruption. Affected firmware versions are: R6400v2 and R6700v3 before 1.0.4.98, R7900 before 1.0.3.18, and R8000 before 1.0.4.46.

MitigationUpdate router firmware to the specified versions (R6400v2/6700v3: 1.0.4.98+, R7900: 1.0.3.18+, R8000: 0.4.46+) or later to remediate the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
R6400 FirmwareOperating system
Affected:< 1.0.4.98
R6700 FirmwareOperating system
Affected:< 1.0.4.98
R7900 FirmwareOperating system
Affected:< 1.0.3.18
R8000 FirmwareOperating system
Affected:< 1.0.4.46

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Check the device label on the router or log into the web admin interface (typically at 192.168.1.1) and look for the model number in the top corner of the dashboard or in the 'Router Info' or 'About' section
    Affected if Model is R6400v2, R6700v3, R7900, or R8000
  2. Check firmware version
    Log into the router web admin interface, navigate to 'Advanced' > 'Administration' > 'Router Update' or 'Advanced' > 'Administration' > 'Firmware Version' to view the currently installed firmware version
    Affected if Firmware version cannot be determined or is not visible in the admin interface
  3. Compare version to affected range for R6400v2 or R6700v3
    If the router model is R6400v2 or R6700v3, compare the installed firmware version against 1.0.4.98. Versions are typically displayed as something like 1.0.4.92 or 1.0.4.96
    Affected if Installed version is less than 1.0.4.98 (for example, 1.0.4.92, 1.0.4.96)
  4. Compare version to affected range for R7900
    If the router model is R7900, compare the installed firmware version against 1.0.3.18
    Affected if Installed version is less than 1.0.3.18 (for example, 1.0.3.10, 1.0.3.16)
  5. Compare version to affected range for R8000
    If the router model is R8000, compare the installed firmware version against 1.0.4.46
    Affected if Installed version is less than 1.0.4.46 (for example, 1.0.4.30, 1.0.4.40)

The environment is affected if the router is an R6400v2, R6700v3, R7900, or R8000 model running firmware version below the respective threshold (1.0.4.98, 1.0.4.98, 1.0.3.18, or 1.0.4.46).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.3.18 / 1.0.4.46 / 1.0.4.98 or later
Fixed in 1.0.3.181.0.4.461.0.4.98
Interim mitigation

Update router firmware to the specified versions (R6400v2/6700v3: 1.0.4.98+, R7900: 1.0.3.18+, R8000: 0.4.46+) or later to remediate the vulnerability.

Recommended fix High confidence

R6400v2/R6700v3: firmware 1.0.4.98 | R7900: firmware 1.0.3.18 | R8000: firmware 1.0.4.46

  1. Identify your specific router model (R6400, R6700, R7900, or R8000) from the affected list
  2. Download the appropriate fixed firmware version from the NETGEAR support website (kb.netgear.com) for your model: R6400v2/R6700v3 use 1.0.4.98, R7900 uses 1.0.3.18, R8000 uses 1.0.4.46
  3. Connect your computer to the router via Ethernet cable
  4. Open a web browser and navigate to routerlogin.net or 192.168.1.1
  5. Log in with your router admin credentials
  6. Navigate to the 'Advanced' tab, then 'Administration' or 'Firmware Update' section
  7. Select 'Upload' or 'Check for Updates' and choose the downloaded firmware file
  8. Wait for the firmware to upload and apply - do not power off the router during this process
Caveat Firmware updates may temporarily interrupt network connectivity; ensure stable power during upgrade to avoid bricked device

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in R6400 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-38515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-38515 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data