CVE-2021-45575
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 confidenceAuthenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) running firmware versions prior to 3.2.16.6, allowing an authenticated attacker to execute arbitrary operating system commands on the 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< 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 exact Orbi model numberLocate the device label on the bottom of the router or satellite unit, or log into the admin web interface and check the device information page to confirm the model is one of: RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850Affected if The device model matches any of the six affected models listed in the CVE
-
Check the current firmware versionLog into the Orbi admin interface (typically at 192.168.1.1 or orbilogin.com), navigate to Administration > Firmware Update or Advanced > Administration > Firmware Upgrade, and record the displayed firmware version numberAffected if The installed firmware version is lower than 3.2.16.6 (for example, 3.2.14.2 or any version < 3.2.16.6)
-
Verify remote management access is enabledIn the Orbi admin interface, go to Advanced > Remote Management or Administration > Remote Management and check if remote access via HTTP/HTTPS from outside the local network is enabledAffected if Remote management is exposed to the internet and the device firmware is below 3.2.16.6
-
Confirm authentication is requiredAttempt to access the admin interface or check if a login is required for the remote management feature; verify that an attacker would need valid credentials to reach the command injection pointAffected if The vulnerability requires authentication, so an attacker with valid admin credentials could exploit it; check for any unauthorized or unexpected admin accounts in the Administration > Advanced > Administrator Settings page
You are affected if you own an RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 device running firmware version 3.2.16.5 or earlier with remote management accessible to an attacker who could obtain valid admin 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
Upgrade NETGEAR Orbi device firmware to version 3.2.16.6 or later to remediate the command injection vulnerability.
3.2.16.6
- Identify the specific NETGEAR mesh model (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850).
- Log into the router’s web UI (e.g., http://routerlogin.net) using an admin account.
- Navigate to Administration > Firmware Update (or Settings > Administration > Firmware).
- Check the currently installed firmware version; confirm it is earlier than 3.2.16.6.
- Download firmware version 3.2.16.6 (or a later stable release) from the NETGEAR support website for your exact model.
- In the Firmware Update page, select the manual update option and upload the downloaded .img file.
- Allow the device to install the firmware and reboot; this may take several minutes.
- After the router restarts, log in again and verify the firmware version now shows 3.2.16.6 or newer.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45575 — 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-45575 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