dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2021-45620

CRITICAL · 9.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.0.58 / 1.0.1.68 or later.
See remediation →
100/100
Remediation priority · Urgent
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 command injection by an unauthenticated attacker. This affects CBR40 before 2.5.0.24, CBR750 before 4.6.3.6, EAX20 before 1.0.0.58, EAX80 before 1.0.1.68, LAX20 before 1.1.6.28, MR60 before 1.0.6.116, MR80 before 1.1.2.20, MS60 before 1.0.6.116, MS80 before 1.1.2.20, MK62 before 1.0.6.116, MK83 before 1.1.2.20, R6400 before 1.0.1.70, R6400v2 before 1.0.4.106, R6700v3 before 1.0.4.106, R6900P before 1.3.3.140, R7000 before 1.0.11.126, R7000P before 1.3.3.140, R7850 before 1.0.5.74, R7900 before 1.0.4.46, R7900P before 1.4.2.84, R7960P before 1.4.2.84, R8000 before 1.0.4.74, R8000P before 1.4.2.84, RAX15 before 1.0.3.96, RAX20 before 1.0.3.96, RAX200 before 1.0.4.120, RAX35v2 before 1.0.3.96, RAX40v2 before 1.0.3.96, RAX43 before 1.0.3.96, RAX45 before 1.0.3.96, RAX50 before 1.0.3.96, RAX75 before 1.0.4.120, RAX80 before 1.0.4.120, RBK752 before 3.2.17.12, RBK852 before 3.2.17.12, RBR750 before 3.2.17.12, RBR850 before 3.2.17.12, RBS750 before 3.2.17.12, RBS850 before 3.2.17.12, RS400 before 1.5.1.80, XR1000 before 1.0.0.58, and XR300 before 1.0.3.68.

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

Unauthenticated command injection vulnerability in multiple NETGEAR router and mesh system devices allowing remote attackers to execute arbitrary system commands via specially crafted requests. The flaw affects the web management interface and requires no authentication.

MitigationApply vendor-supplied firmware updates to versions at or above the specified thresholds for each affected model. If updates are unavailable, restrict administrative interface access to trusted networks or disable remote management.

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
Cbr40 FirmwareOperating system
Affected:< 2.5.0.24
Cbr750 FirmwareOperating system
Affected:< 4.6.3.6
Eax20 FirmwareOperating system
Affected:< 1.0.0.58
Eax80 FirmwareOperating system
Affected:< 1.0.1.68
Lax20 FirmwareOperating system
Affected:< 1.1.6.28
Mr60 FirmwareOperating system
Affected:< 1.0.6.116
Ms60 FirmwareOperating system
Affected:< 1.0.6.116
R6400v2 FirmwareOperating system
Affected:< 1.0.4.118

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify your NETGEAR device model
    Locate the model number printed on the device label or access the admin interface to view device information
    Affected if The device model is one of: Cbr40, Cbr750, Eax20, Eax80, Lax20, Mr60, Ms60, or R6400v2
  2. Determine the installed firmware version
    Access the router web management interface, typically at 192.168.1.1 or 192.168.0.1, and navigate to Settings > Administration > Firmware Update, or check the device label for firmware version printed
    Affected if The firmware version is below: Cbr40 < 2.5.0.24, Cbr750 < 4.6.3.6, Eax20 < 1.0.0.58, Eax80 < 1.0.1.68, Lax20 < 1.1.6.28, Mr60 < 1.0.6.116, Ms60 < 1.0.6.116, R6400v2 < 1.0.4.118
  3. Verify if the web management interface is externally accessible
    Check your router firewall or port forwarding settings to determine if ports 80 or 443 (HTTP/HTTPS) are open to the WAN/internet, or attempt to access your public IP address on ports 80/443 from an external network
    Affected if The web management interface is reachable from the internet (WAN side) on ports 80 or 443
  4. Inspect for signs of unauthorized command execution
    Review router system logs for unexpected commands, unfamiliar processes, or suspicious DNS changes. Check for new user accounts, modified startup scripts, or unexpected network connections
    Affected if Logs contain commands or configurations that were not initiated by legitimate administrators, or unexpected files/processes exist on the device

Your device is affected if it is one of the listed models AND runs firmware versions below the specified thresholds AND the web management interface is exposed to the network where attackers could reach it.

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.0.58 / 1.0.1.68 / 1.0.4.118 or later
Fixed in 1.0.0.581.0.1.681.0.4.118
Interim mitigation

Apply vendor-supplied firmware updates to versions at or above the specified thresholds for each affected model. If updates are unavailable, restrict administrative interface access to trusted networks or disable remote management.

Recommended fix High confidence

Upgrade to firmware version 2.5.0.24 or later (CBR40), 4.6.3.6 or later (CBR750), 1.0.0.58 or later (EAX20), 1.0.1.68 or later (EAX80), 1.1.6.28 or later (LAX20), 1.0.6.116 or later (MR60/MS60), 1.0.4.118 or later (R6400v2), or the specific fixed version for your model as listed in the official secu

  1. 1. Identify the specific NETGEAR router or mesh system model from the affected list (CBR40, CBR750, EAX20, EAX80, LAX20, MR60, MS60, R6400v2, or other models listed in the official description).
  2. 2. Download the latest firmware for your specific model from the official NETGEAR support page at kb.netgear.com.
  3. 3. Access the router's web management interface by navigating to routerlogin.net or using the router's IP address (typically 192.168.1.1).
  4. 4. Log in with administrator credentials.
  5. 5. Navigate to the Administration or Advanced settings section.
  6. 6. Select the Firmware Update option.
  7. 7. Upload the downloaded firmware file and initiate the update.
  8. 8. Wait for the update to complete and the device to reboot - do not power off the device during this process.
Caveat Firmware updates may reset some custom configurations; backup router settings before updating if possible.

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

Fix this in Cbr40 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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