dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2021-45613

CRITICAL · 9.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.0.74 / 1.0.3.96 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, D7000v2 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, MR80 before 1.1.2.20, MS80 before 1.1.2.20, RAX15 before 1.0.3.96, RAX20 before 1.0.3.96, RAX200 before 1.0.4.120, RAX45 before 1.0.3.96, RAX50 before 1.0.3.96, RAX43 before 1.0.3.96, RAX40v2 before 1.0.3.96, RAX35v2 before 1.0.3.96, RAX75 before 1.0.4.120, RAX80 before 1.0.4.120, RBK752 before 3.2.17.12, RBR750 before 3.2.17.12, RBS750 before 3.2.17.12, RBK852 before 3.2.17.12, RBR850 before 3.2.17.12, RBS850 before 3.2.17.12, and XR1000 before 1.0.0.58.

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 NETGEAR router and mesh system firmware. An attacker can execute arbitrary OS commands on affected devices without authentication, leading to complete device compromise.

MitigationUpdate all affected NETGEAR devices to the patched firmware versions specified for each model. If immediate patching is not feasible, disable remote management interfaces and restrict network access to device administration panels.

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
D7000v2 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
Ms60 FirmwareOperating system
Affected:< 1.0.6.116
Rax15 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 management interface and navigate to the Status or Advanced > Administration > Router Information page to view the model name. Alternatively, check the physical device label or packaging.
    Affected if The model is one of: Cbr40, Cbr750, D7000v2, Lax20, Mk62, Mr60, Ms60, or Rax15.
  2. Check the installed firmware version
    In the router web interface, go to Status > Router Information or Advanced > Administration > Firmware Update to view the current firmware version number.
    Affected if The firmware version cannot be determined or is not visible in the interface.
  3. Compare firmware version for Cbr40
    If the device is a Cbr40, compare your firmware version against 2.5.0.24. Versions below 2.5.0.24 are affected.
    Affected if Cbr40 firmware version is less than 2.5.0.24.
  4. Compare firmware version for Cbr750
    If the device is a Cbr750, compare your firmware version against 4.6.3.6. Versions below 4.6.3.6 are affected.
    Affected if Cbr750 firmware version is less than 4.6.3.6.
  5. Compare firmware version for D7000v2
    If the device is a D7000v2, compare your firmware version against 1.0.0.74. Versions below 1.0.0.74 are affected.
    Affected if D7000v2 firmware version is less than 1.0.0.74.
  6. Compare firmware version for Lax20
    If the device is a Lax20, compare your firmware version against 1.1.6.28. Versions below 1.1.6.28 are affected.
    Affected if Lax20 firmware version is less than 1.1.6.28.

The device is affected if it is one of the listed NETGEAR models (Cbr40, Cbr750, D7000v2, Lax20, Mk62, Mr60, Ms60, or Rax15) and its current firmware version falls below the corresponding patched version for that 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.74 / 1.0.3.96 / 1.0.6.116 or later
Fixed in 1.0.0.741.0.3.961.0.6.116
Interim mitigation

Update all affected NETGEAR devices to the patched firmware versions specified for each model. If immediate patching is not feasible, disable remote management interfaces and restrict network access to device administration panels.

Recommended fix High confidence

Upgrade to the specific fixed firmware version for your model as listed on NETGEAR's support site (kb.netgear.com)

  1. 1. Identify your NETGEAR router model from the affected list (CBR40, CBR750, D7000v2, LAX20, MK62, MR60, MS60, RAX15, or other affected models listed in the official description).
  2. 2. Navigate to the NETGEAR support website (kb.netgear.com) or download center for your specific model.
  3. 3. Locate the firmware download section for your model.
  4. 4. Download the latest firmware version that meets or exceeds the fixed version for your device: CBR40: 2.5.0.24, CBR750: 4.6.3.6, D7000v2: 1.0.0.74, LAX20: 1.1.6.28, MK62/MR60/MS60: 1.0.6.116, RAX15/RAX20/RAX40v2/RAX35v2/RAX43/RAX45/RAX50: 1.0.3.96, MR80/MS80: 1.1.2.20, RAX200/RAX75/RAX80: 1.0.4.120, RBK752/RBR750/RBS750/RBK852/RBR850/RBS850: 3.2.17.12, XR1000: 1.0.0.58.
  5. 5. Access your router's web management interface by entering the router's IP address in a web browser.
  6. 6. Log in with administrator credentials.
  7. 7. Navigate to the Advanced settings > Administration > Firmware Update section.
  8. 8. Select the option to upload the downloaded firmware file.
Caveat Minor: Firmware updates may temporarily disrupt network connectivity; ensure stable power during upgrade

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-45613 — 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-45613 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