CVE-2021-45545
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 R7850 before 1.0.5.74, R7900P before 1.4.2.84, R7960P before 1.4.2.84, R8000 before 1.0.4.74, R8000P before 1.4.2.84, RAX200 before 1.0.4.120, RAX75 before 1.0.4.120, RAX80 before 1.0.4.120, RBK852 before 3.2.17.12, RBR850 before 3.2.17.12, and RBS850 before 3.2.17.12.
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 confidenceThis is an authenticated command injection vulnerability affecting multiple NETGEAR router models. An authenticated attacker can execute arbitrary commands on the affected devices through improper input validation in the web management interface. The vulnerability affects specific firmware versions of R7850, R7900P, R7960P, R8000, R8000P, RAX200, RAX75, RAX80, RBK852, RBR850, and RBS850 devices.
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.5.74< 1.4.2.84< 1.4.2.84< 1.0.4.74< 1.4.2.84< 1.0.4.120< 1.0.4.120< 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
- 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 the NETGEAR router modelLocate the device label on the router or log into the web management interface to view the model nameAffected if The model is one of: R7850, R7900P, R7960P, R8000, R8000P, RAX200, RAX75, RAX80, RBK852, RBR850, or RBS850
-
Check the installed firmware versionLog into the router web interface and navigate to Administration > Firmware Update or check the router status page for the current firmware versionAffected if The firmware version cannot be verified or is below the patched version for your model
-
Compare your firmware version to the affected rangesCompare your installed version against: R7850 < 1.0.5.74, R7900P/R7960P/R8000P < 1.4.2.84, R8000 < 1.0.4.74, RAX200/RAX75/RAX80 < 1.0.4.120Affected if Your installed version falls below the patched version for your specific model
-
Verify web management interface accessibilityConfirm whether the router web management interface is accessible from the network. This vulnerability requires an authenticated session to exploit.Affected if The web interface is exposed and an attacker could potentially obtain valid authentication credentials
You are affected if your router model matches one of the listed products AND your current firmware version is below the patched version threshold AND the web management interface is accessible to an attacker.
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.4.741.0.4.1201.0.5.74
Apply the available firmware updates from NETGEAR to upgrade to the patched versions (R7850: 1.0.5.74, R7900P/R7960P/R8000P: 1.4.2.84, R8000: 1.0.4.74, RAX200/RAX75/RAX80: 1.0.4.120, RBK852/RBR850/RBS850: 3.2.17.12) or later.
Upgrade to firmware version 1.0.5.74 (R7850), 1.4.2.84 (R7900P/R7960P/R8000P), 1.0.4.74 (R8000), or 1.0.4.120 (RAX200/RAX75/RAX80) as listed in the CVE description
- 1. Identify the exact NETGEAR router model number from the affected list (R7850, R7900P, R7960P, R8000, R8000P, RAX200, RAX75, or RAX80)
- 2. Access the router's web administration interface by entering the router's IP address in a web browser
- 3. Log in with administrator credentials
- 4. Navigate to the Administration or Advanced settings section
- 5. Locate the Firmware Update option
- 6. Download the appropriate fixed firmware version from NETGEAR's official support site (kb.netgear.com) matching your model: R7850→1.0.5.74, R7900P→1.4.2.84, R7960P→1.4.2.84, R8000→1.0.4.74, R8000P→1.4.2.84, RAX200→1.0.4.120, RAX75→1.0.4.120, RAX80→1.0.4.120
- 7. Upload the firmware file through the router's web interface and initiate the update
- 8. Wait for the update to complete and the router to reboot automatically
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45545 — 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-45545 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