CVE-2021-45592
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 RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, and RBS850 before 3.2.16.6.
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 NETGEAR Orbi mesh WiFi systems (models RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) running firmware versions prior to 3.2.16.6. An attacker with valid credentials can inject and execute arbitrary OS commands on the affected devices due to insufficient input sanitization in the firmware's web 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< 3.2.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6CVSS 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 Orbi device modelCheck the device label on the unit or log into the web management interface and look for the model number in the status or settings pageAffected if The model is not one of RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 (those are the only affected models)
-
Check the installed firmware versionLog into the Orbi web interface and navigate to the Administration or Firmware Update section to view the current firmware versionAffected if The firmware version is anything less than 3.2.16.6 (for example, 3.2.14.2, 3.2.15.1, etc.)
-
Confirm web management interface is accessibleAttempt to access the Orbi router's web interface by entering the device IP address in a web browserAffected if The web interface is reachable from the network where an attacker could obtain or use valid credentials
-
Determine if default credentials are in useCheck if the administrative password is still set to the default or if it has been changed to a custom valueAffected if Default credentials are still active, making it easier for an attacker to obtain valid authentication
-
Verify input fields in the web interface allow commandsThis is a vulnerability detail check - the flaw exists in how the firmware processes input in certain web interface fields before version 3.2.16.6Affected if The device runs a vulnerable firmware version (less than 3.2.16.6) and an attacker can authenticate to the web interface
You are affected if you have an Orbi model RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 running firmware version lower than 3.2.16.6 and the web management interface is accessible to someone with valid credentials.
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 · scoped3.2.16.6
Update NETGEAR Orbi firmware to version 3.2.16.6 or later. Restrict administrative access to trusted users only and change default credentials to limit the attack surface.
Firmware 3.2.16.6 or later
- Identify your specific NETGEAR Orbi model from the affected list: Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, or Rbs850
- Visit the official NETGEAR support website (kb.netgear.com) and navigate to the firmware download section for your model
- Download firmware version 3.2.16.6 or later for your specific device model
- Access the router's web management interface by entering the router's IP address in a web browser
- Log in with administrator credentials
- Navigate to the Administration or Settings section and select Firmware Update
- Upload the downloaded firmware file and initiate the update process
- Wait for the router to reboot and verify the firmware version shows 3.2.16.6 or later
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-45592 — 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-45592 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