dbcve.org
Lax20 FirmwareOperating system · Netgear

CVE-2021-45549

MEDIUM · 6.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.4.118 / 1.0.11.116 or later.
See remediation →
70/100
Remediation priority · Elevated
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 authenticated user. This affects LAX20 before 1.1.6.28, MK62 before 1.1.6.122, MR60 before 1.1.6.122, MS60 before 1.1.6.122, 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, RS400 before 1.5.1.80, 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

Multiple NETGEAR router models contain a command injection vulnerability in their web management interface. An attacker with valid administrative credentials can inject arbitrary OS commands through insufficient input sanitization in certain parameters, potentially gaining full control of the device.

MitigationUpdate affected devices to the specified firmware versions. If updates are unavailable, minimize exposure by disabling remote administration, using strong unique credentials, and restricting access to trusted networks only.

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
Lax20 FirmwareOperating system
Affected:< 1.1.6.28
Mk62 FirmwareOperating system
Affected:< 1.1.6.122
Mr60 FirmwareOperating system
Affected:< 1.1.6.122
Ms60 FirmwareOperating system
Affected:< 1.1.6.122
R6400 FirmwareOperating system
Affected:< 1.0.4.118
R6700 FirmwareOperating system
Affected:< 1.0.4.118
R6900p FirmwareOperating system
Affected:< 1.3.3.140
R7000 FirmwareOperating system
Affected:< 1.0.11.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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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 router model
    Locate the model number on the device label or log into the web management interface and check the status or administration page for the model name
    Affected if The model is one of: Lax20, Mk62, Mr60, Ms60, R6400, R6700, R6900p, or R7000
  2. Check the installed firmware version
    Log into the web management interface and navigate to the Administration or Firmware Update section to view the current firmware version
    Affected if The firmware version is below: Lax20 < 1.1.6.28, Mk62/Mr60/Ms60 < 1.1.6.122, R6400/R6700 < 1.0.4.118, R6900p < 1.3.3.140, R7000 < 1.0.11.116
  3. Verify if web management interface is accessible
    Check if the router web interface is reachable on the default HTTP/HTTPS ports (80/443) either locally or remotely if remote administration is enabled
    Affected if The web management interface is exposed to untrusted networks
  4. Confirm remote administration settings
    In the web management interface, check the Administration > Remote Management or similar section to see if remote access is enabled
    Affected if Remote administration is enabled and the interface is accessible from outside the local network

The device is affected if it matches one of the affected models AND its firmware version is below the specified fixed version AND the web management interface is accessible to the attacker.

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.118 / 1.0.11.116 / 1.1.6.28 or later
Fixed in 1.0.4.1181.0.11.1161.1.6.28
Interim mitigation

Update affected devices to the specified firmware versions. If updates are unavailable, minimize exposure by disabling remote administration, using strong unique credentials, and restricting access to trusted networks only.

Recommended fix High confidence

Upgrade to firmware version 1.1.6.28 (LAX20), 1.1.6.122 (MK62/MR60/MS60), 1.0.4.118 (R6400/R6700), 1.3.3.140 (R6900P), or 1.0.11.116 (R7000) or later as applicable to your model

  1. 1. Identify the exact NETGEAR router model (check the device label or web interface)
  2. 2. Access the router's web interface (typically 192.168.1.1 or 192.168.0.1) and check the current firmware version under Administration > Firmware Update or similar
  3. 3. Visit kb.netgear.com and search for the specific router model to find the latest firmware
  4. 4. Download the appropriate firmware update for your model (must be version 1.1.6.28+ for LAX20, 1.1.6.122+ for MK62/MR60/MS60, 1.0.4.118+ for R6400/R6700, 1.3.3.140+ for R6900P, or 1.0.11.116+ for R7000)
  5. 5. In the router's web interface, navigate to the firmware upgrade section and upload the downloaded firmware file
  6. 6. Wait for the firmware to upload and install - the router will automatically reboot
  7. 7. After reboot, verify the new firmware version is installed correctly
Caveat Firmware updates typically preserve settings but always backup router configuration before upgrading as a precaution

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

Fix this in Lax20 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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