dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2021-45621

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 3.2.18.2, EAX20 before 1.0.0.58, EAX80 before 1.0.1.68, EX3700 before 1.0.0.94, EX3800 before 1.0.0.94, EX6120 before 1.0.0.64, EX6130 before 1.0.0.44, EX7000 before 1.0.1.104, EX7500 before 1.0.0.74, LAX20 before 1.1.6.28, MR60 before 1.0.6.116, MS60 before 1.0.6.116, R6300v2 before 1.0.4.52, 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, R7100LG before 1.0.0.72, 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, R8300 before 1.0.2.154, R8500 before 1.0.2.154, 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, RBK852 before 3.2.17.12, RBR750 before 3.2.17.12, RBR850 before 3.2.17.12, RBR850 before 3.2.17.12, RBS750 before 3.2.17.12, RBS850 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 firmware versions. An attacker can execute arbitrary OS commands without authentication due to insufficient input sanitization in a web interface component.

MitigationApply vendor-supplied firmware updates to all affected devices (upgrade to versions at or above the specified fix versions listed in the advisory). If updates are unavailable, disable remote management interfaces and restrict LAN access.

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:< 3.2.18.2
Eax20 FirmwareOperating system
Affected:< 1.0.0.58
Eax80 FirmwareOperating system
Affected:< 1.0.1.68
Rax15 FirmwareOperating system
Affected:< 1.0.3.96
Rax20 FirmwareOperating system
Affected:< 1.0.3.96
Rax200 FirmwareOperating system
Affected:< 1.0.4.120
Rax35v2 FirmwareOperating system
Affected:< 1.0.3.96

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 the NETGEAR device model
    Log into the router web interface (typically at 192.168.1.1 or 192.168.0.1) and check the status or administration page for the exact model name (e.g., CBR40, EAX20, RAX200). The model is also usually printed on the physical device label.
    Affected if The device model matches one of: CBR40, CBR750, EAX20, EAX80, RAX15, RAX20, RAX200, or RAX35v2
  2. Determine 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. Alternatively, check the status dashboard which typically displays the firmware version.
    Affected if The displayed firmware version is lower than the fix version for your model (CBR40 < 2.5.0.24, CBR750 < 3.2.18.2, EAX20 < 1.0.0.58, EAX80 < 1.0.1.68, RAX15/RAX20/RAX35v2 < 1.0.3.96, RAX200 < 1.0.4.120)
  3. Check if remote management is enabled
    In the router web interface, go to Advanced > Remote Management (or Administration > Remote Management) and verify whether the 'Enable Remote Management' or 'Allow remote access' option is checked/enabled.
    Affected if Remote management is enabled and the web interface is accessible from the WAN (internet), making the vulnerability exploitable from outside the local network
  4. Verify web interface accessibility
    Attempt to access the router login page from a browser. If remote management is ON, try accessing the router's public IP address on port 8080 or 8443 (common remote management ports). Use a tool like nmap to check if ports 80, 443, 8080, or 8443 are open on the WAN interface.
    Affected if The router web management interface is reachable from the network segment being assessed (LAN or WAN depending on threat model)

The device is affected if it is one of the listed NETGEAR models running firmware version lower than the specified fix version, and the web interface component (where the command injection exists) is accessible.

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.3.96 or later
Fixed in 1.0.0.581.0.1.681.0.3.96
Interim mitigation

Apply vendor-supplied firmware updates to all affected devices (upgrade to versions at or above the specified fix versions listed in the advisory). If updates are unavailable, disable remote management interfaces and restrict LAN access.

Recommended fix High confidence

Upgrade to firmware version 2.5.0.24 (CBR40), 3.2.18.2 (CBR750), 1.0.0.58 (EAX20), 1.0.1.68 (EAX80), 1.0.3.96 (RAX15/RAX20/RAX35v2), 1.0.4.120 (RAX200/RAX75/RAX80), or later fixed versions as listed in the NETGEAR security advisory.

  1. 1. Identify the exact NETGEAR device model from the affected list (CBR40, CBR750, EAX20, EAX80, RAX15, RAX20, RAX200, RAX35v2, or other affected models).
  2. 2. Access the device administration interface via web browser (typically at routerlogin.net or 192.168.1.1).
  3. 3. Navigate to the Firmware Update or Administration section to check the current installed firmware version.
  4. 4. Compare the current firmware version against the fixed version for your specific model (e.g., CBR40: 2.5.0.24, CBR750: 3.2.18.2, EAX20: 1.0.0.58, EAX80: 1.0.1.68, RAX15/RAX20/RAX35v2: 1.0.3.96, RAX200/RAX75/RAX80: 1.0.4.120).
  5. 5. If the current version is lower than the fixed version, download the latest firmware from the official NETGEAR support website (support.netgear.com) for your specific model.
  6. 6. Upload and apply the firmware update through the device administration interface, or use the NETGEAR Nighthawk/Orbi mobile app if applicable.
  7. 7. After the update completes and the device reboots, verify the new firmware version matches the fixed version.
  8. 8. Confirm the command injection vulnerability is no longer present by ensuring the device is not exposing vulnerable services to unauthenticated network attackers.
Caveat NETGEAR firmware upgrades typically preserve settings; however, a factory reset may be recommended after major firmware updates to ensure stability and clear any residual vulnerabilities.

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

Fix this in Cbr40 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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