CVE-2021-45614
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 · uneditedCertain NETGEAR devices are affected by command injection by an unauthenticated attacker. This affects 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, 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 confidenceMultiple NETGEAR router models contain a command injection vulnerability allowing unauthenticated attackers to execute arbitrary commands on the device. The vulnerability stems from insufficient input validation in web interface components, enabling attackers to inject OS commands through specially crafted HTTP requests. This results in full compromise of the affected device.
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< 1.0.0.74< 1.1.6.28< 1.0.6.116< 1.0.6.116< 1.0.6.116< 1.0.3.96< 1.0.3.96< 1.0.4.120CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR router modelLocate the model number on the device label or log into the web interface and check the router status page for the exact model designation (e.g., D7000v2, Lax20, Mk62, Mr60, Ms60, Rax15, Rax20, Rax200)Affected if The model is one of: D7000v2, Lax20, Mk62, Mr60, Ms60, Rax15, Rax20, or Rax200
-
Check the installed firmware versionLog into the router web interface and navigate to the Administration or Firmware Update section to view the current firmware version, or access the router via telnet/SSH if enabled and run 'nvram get firmware_version' or similar commandAffected if Unable to retrieve firmware version or version cannot be confirmed
-
Compare firmware version against affected rangesCompare your installed firmware version to these thresholds: D7000v2 < 1.0.0.74, Lax20 < 1.1.6.28, Mk62 < 1.0.6.116, Mr60 < 1.0.6.116, Ms60 < 1.0.6.116, Rax15 < 1.0.3.96, Rax20 < 1.0.3.96, Rax200 < 1.0.4.120Affected if The installed firmware version is lower than the specified threshold for your model
-
Confirm web interface accessibilityAttempt to access the router login page via HTTP/HTTPS on the router LAN IP address (typically 192.168.1.1) from a browserAffected if The web management interface is reachable (this is the attack surface for command injection)
If the router model matches one of the eight affected models AND the installed firmware version is below the specified threshold for that model, the device is vulnerable to CVE-2021-45614 command injection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.0.741.0.3.961.0.4.120
Apply the vendor-supplied firmware updates for each affected model (versions specified in the advisory). For devices that cannot be updated, restrict administrative interface access to trusted networks only and disable remote management features.
Device-specific firmware: D7000v2 to 1.0.0.74 | LAX20 to 1.1.6.28 | MK62/MR60/MS60 to 1.0.6.116 | RAX15/RAX20/RAX40v2/RAX43/RAX45/RAX50/RAX35v2 to 1.0.3.96 | RAX200/RAX75/RAX80 to 1.0.4.120 | RBK752/RBR750/SBS750/RBK852/RBR850/RBS850 to 3.2.17.12 | XR1000 to 1.0.0.58
- 1. Identify the exact NETGEAR device model from the affected list (D7000v2, LAX20, MK62, MR60, MS60, RAX15, RAX20, RAX200, RAX45, RAX50, RAX43, RAX40v2, RAX35v2, RAX75, RAX80, RBK752, RBR750, RBS750, RBK852, RBR850, RBS850, XR1000)
- 2. Access the device administration interface via web browser (typically http://routerlogin.net or http://192.168.1.1)
- 3. Navigate to the firmware update section (usually under Settings > Administration > Firmware Update or similar)
- 4. Check current firmware version under the router status or advanced settings
- 5. Download the appropriate fixed firmware version from the official NETGEAR support website (kb.netgear.com) for your specific model
- 6. In the router admin interface, select the option to manually upload firmware and choose the downloaded file
- 7. Wait for the firmware upload and installation to complete - do not power off the device during this process
- 8. After reboot, verify the new firmware version matches the fixed release (1.0.0.74, 1.1.6.28, 1.0.6.116, 3.2.17.12, or 1.0.0.58 depending on model)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-45614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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