dbcve.org
R8000 FirmwareOperating system · Netgear

CVE-2021-45532

HIGH · 7.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.4.76 or later.
See remediation →
80/100
Remediation priority · High
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
NETGEAR R8000 devices before 1.0.4.76 are affected by command injection by an authenticated user.

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 · high confidence

NETGEAR R8000 routers before firmware version 1.0.4.76 contain a command injection vulnerability that allows an authenticated attacker to execute arbitrary operating system commands on the device through the web management interface.

MitigationUpgrade NETGEAR R8000 firmware to version 1.0.4.76 or later to remediate this 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
R8000 FirmwareOperating system
Affected:< 1.0.4.76

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Confirm device model is NETGEAR R8000
    Access the router web management interface and check the device information page, or log into the router and look for the model number in the status or administration section
    Affected if The device is not a NETGEAR R8000 router - this CVE only applies to that specific model
  2. Check the installed firmware version
    In the router web interface, navigate to Administration > Router Update or Advanced > Administration > Firmware Update to view the current firmware version. Compare it to 1.0.4.76
    Affected if The firmware version is less than 1.0.4.76 - versions before this are affected
  3. Verify web management interface is enabled
    In the router web interface, check Advanced > Administration > Web Management or similar section to confirm the HTTP/HTTPS management interface is turned on
    Affected if The web management interface is disabled, exploitation is not possible through this attack vector
  4. Check if remote management access is enabled
    In the router web interface, look for Remote Management settings (usually under Advanced > Administration > Remote Management) to see if management access from WAN/internet is permitted
    Affected if Remote management is enabled, the attack surface expands to include remote authenticated attackers rather than only local network attackers

The environment is affected if the device is a NETGEAR R8000 router running firmware version earlier than 1.0.4.76 with the web management interface enabled.

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.4.76 or later
Fixed in 1.0.4.76
Interim mitigation

Upgrade NETGEAR R8000 firmware to version 1.0.4.76 or later to remediate this vulnerability.

Recommended fix High confidence

1.0.4.76 (or later)

  1. Check the current firmware version in the router's web UI under Administration > Firmware Update.
  2. Download firmware version 1.0.4.76 (or the latest available) from the official NETGEAR support site for the R8000.
  3. In the router's web UI, go to Advanced > Administration > Firmware Update, click Browse, select the downloaded .img file, and then click Upload.
  4. Wait for the upload to finish; the router will automatically reboot.
  5. After the reboot, log in and confirm that the firmware version now shows 1.0.4.76 or later.
  6. Re-apply any custom settings if needed.

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

Fix this in R8000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45532 — 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-45532 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