dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2021-45622

CRITICAL · 9.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.0.58 / 1.0.0.74 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, EX7500 before 1.0.0.74, LAX20 before 1.1.6.28, MK62 before 1.0.6.116, MR60 before 1.0.6.116, MS60 before 1.0.6.116, R6400 before 1.0.1.70, R6400v2 before 1.0.4.118, R6700v3 before 1.0.4.118, R6900P before 1.3.3.140, R7000 before 1.0.11.116, R7000P before 1.3.3.140, R7850 before 1.0.5.68, R7900 before 1.0.4.38, R7900P before 1.4.2.84, R7960P before 1.4.2.84, R8000 before 1.0.4.68, 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 device firmware. An attacker can inject and execute arbitrary operating system commands without authentication, likely through a web interface parameter that fails to properly sanitize user input before passing it to a system call.

MitigationApply available firmware updates from NETGEAR for each affected model to the specified versions. If patching is not immediately possible, restrict exposure by disabling remote administration or placing devices behind a firewall.

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
Ex7500 FirmwareOperating system
Affected:< 1.0.0.74
Lax20 FirmwareOperating system
Affected:< 1.1.6.28
Mk62 FirmwareOperating system
Affected:< 1.0.6.116
Mr60 FirmwareOperating system
Affected:< 1.0.6.116

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 on the device label or access the router web interface (typically at 192.168.1.1) to view the device information page. Confirm the model is one of: Cbr40, Cbr750, Eax20, Eax80, Ex7500, Lax20, Mk62, or Mr60.
    Affected if The device model matches one of the eight affected models listed in the CVE.
  2. Determine the currently installed firmware version
    Access the router web interface, navigate to the Administration or Advanced settings section, and look for a Firmware Update or Router Status page that displays the current firmware version. Alternatively, check the device label or documentation for the installed version.
    Affected if The installed firmware version cannot be confirmed or is below the patched version threshold for your model.
  3. Compare installed version against CVE thresholds
    Reference the affected version ranges: Cbr40 < 2.5.0.24, Cbr750 < 4.6.3.6, Eax20 < 1.0.0.58, Eax80 < 1.0.1.68, Ex7500 < 1.0.0.74, Lax20 < 1.1.6.28, Mk62 < 1.0.6.116, Mr60 < 1.0.6.116. Compare your installed version to these specific thresholds.
    Affected if The installed version is lower than the safe version number for your specific model.
  4. Assess web interface accessibility
    Determine if the router web administration interface is accessible from the internet (remote management enabled) or only from the local network. Check the router settings under Remote Management, Access Control, or Administration > Router Management Access.
    Affected if Remote administration is enabled and the device is internet-facing, increasing the likelihood of external exploitation attempts.

You are affected if your NETGEAR device model is one of the eight listed models and the installed firmware version is below the patched version threshold for that specific model.

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.0.74 / 1.0.1.68 or later
Fixed in 1.0.0.581.0.0.741.0.1.68
Interim mitigation

Apply available firmware updates from NETGEAR for each affected model to the specified versions. If patching is not immediately possible, restrict exposure by disabling remote administration or placing devices behind a firewall.

Recommended fix High confidence

Firmware version equal to or newer than: 2.5.0.24 (CBR40), 4.6.3.6 (CBR750), 1.0.0.58 (EAX20), 1.0.1.68 (EAX80), 1.0.0.74 (EX7500), 1.1.6.28 (LAX20), 1.0.6.116 (MK62/MR60)

  1. 1. Identify your NETGEAR device model number (located on the device label or web UI)
  2. 2. Visit the NETGEAR support website (support.netgear.com) or the specific KB article at kb.netgear.com
  3. 3. Enter your device model number and locate the firmware download section
  4. 4. Download the firmware version equal to or newer than the fixed version for your device: CBR40: 2.5.0.24, CBR750: 4.6.3.6, EAX20: 1.0.0.58, EAX80: 1.0.1.68, EX7500: 1.0.0.74, LAX20: 1.1.6.28, MK62: 1.0.6.116, MR60: 1.0.6.116
  5. 5. Access your router's web management interface (typically at 192.168.1.1 or routerlogin.net)
  6. 6. Navigate to Administration > Firmware Update or similar menu option
  7. 7. Select 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 during update)
Caveat Standard firmware update risk: ensure stable power during upgrade; some settings may reset to defaults after update

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

Fix this in Cbr40 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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