CVE-2021-45550
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 authenticated user. This affects D3600 before 1.0.0.76, D6000 before 1.0.0.78, D6100 before 1.0.0.63, D6220 before 1.0.0.52, D6400 before 1.0.0.86, D7800 before 1.0.1.56, D8500 before 1.0.3.44, DGN2200Bv4 before 1.0.0.109, DGN2200v4 before 1.0.0.110, R6250 before 1.0.4.34, R6300v2 before 1.0.4.34, R6400 before 1.0.1.46, R6400v2 before 1.0.2.66, R6700 before 1.0.2.6, R6700v3 before 1.0.2.66, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R7000 before 1.0.9.42, R7000P before 1.3.1.64, R7100LG before 1.0.0.50, R7300 before 1.0.0.70, R7900 before 1.0.3.8, R7900P before 1.4.1.30, R8000 before 1.0.4.28, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, WNDR3400v3 before 1.0.1.24, WNR3500Lv2 before 1.2.0.62, and XR500 before 2.3.2.56.
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 confidenceAuthenticated command injection vulnerability in multiple NETGEAR router models. An attacker with valid admin credentials can execute arbitrary commands on the underlying operating system through unsanitized input in the web management interface.
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.76< 1.0.0.78< 1.0.0.63< 1.0.0.52< 1.0.0.86< 1.0.1.56< 1.0.3.44< 1.0.0.109CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the model number on the device label or check the web management interface status page for the exact model designation (e.g., D3600, D6000, D6100, D6220, D6400, D7800, D8500, DGN2200B)Affected if The model matches one of the affected products listed in the CVE (D3600, D6000, D6100, D6220, D6400, D7800, D8500, Dgn2200b)
-
Check firmware versionAccess the router web management interface, navigate to the status or administration page, and record the firmware version number displayedAffected if The installed firmware version is lower than the specified threshold for your model: D3600 < 1.0.0.76, D6000 < 1.0.0.78, D6100 < 1.0.0.63, D6220 < 1.0.0.52, D6400 < 1.0.0.86, D7800 < 1.0.1.56, D8500 < 1.0.3.44, DGN2200B < 1.0.0.109
-
Confirm web management interface is enabledVerify that the HTTP/HTTPS web interface is accessible by attempting to reach the router login page at the default gateway IP (typically 192.168.1.1 or 192.168.0.1)Affected if The web management interface is accessible and responds to login requests
-
Check remote management settingIn the web management interface, locate the remote management or external access settings (usually under Advanced > Administration > Remote Management) and verify if remote access is enabledAffected if Remote management is enabled, allowing exploitation from outside the local network
-
Verify admin account existsCheck if an administrator account is configured on the device by examining the user management or administrator settings in the web interfaceAffected if At least one admin account exists with credentials that could be compromised or used for authentication
Your environment is affected if you own one of the listed NETGEAR router models and the installed firmware version is below the specified threshold for that model, with the web management interface accessible and an admin account configured.
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.521.0.0.631.0.0.76
Update affected NETGEAR devices to the specified firmware versions. If updates are unavailable, restrict administrative access to trusted IP addresses only and disable remote management.
Model-specific fixed firmware: D3600 1.0.0.76, D6000 1.0.0.78, D6100 1.0.0.63, D6220 1.0.0.52, D6400 1.0.0.86, D7800 1.0.1.56, D8500 1.0.3.44, DGN2200Bv4 1.0.0.109, DGN2200v4 1.0.0.110, R6250 1.0.4.34, R6300v2 1.0.4.34, R6400 1.0.1.46, R6400v2 1.0.2.66, R6700 1.0.2.6, R6700v3 1.0.2.66, R6900 1.0.2.4
- 1. Identify the specific NETGEAR router model from the affected list (D3600, D6000, D6100, D6220, D6400, D7800, D8500, DGN2200Bv4, DGN2200v4, R6250, R6300v2, R6400, R6400v2, R6700, R6700v3, R6900, R6900P, R7000, R7000P, R7100LG, R7300, R7900, R7900P, R8000, R8000P, R8300, R8500, WNDR3400v3, WNR3500Lv2, or XR500)
- 2. Access the router's web management interface by entering the router's IP address in a web browser
- 3. Log in with administrator credentials
- 4. Navigate to the 'Advanced' or 'Administration' section
- 5. Select 'Firmware Update' or 'Router Update' option
- 6. Check for available updates using the 'Check' or 'Upload' button
- 7. Download the appropriate firmware version from the NETGEAR support website (kb.netgear.com) matching your model
- 8. Upload and apply the fixed firmware version specific to your 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-45550 — 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-45550 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