CVE-2021-45537
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 RAX200 before 1.0.3.106, RAX75 before 1.0.3.106, RAX80 before 1.0.3.106, 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 multiple NETGEAR router firmware versions. An authenticated attacker can execute arbitrary OS commands on affected devices through 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.3.106< 1.0.3.106< 1.0.3.106all versions< 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 router modelLocate the model number label on the device or check the web management interface System Info or Administration section for the exact model designation (e.g., RAX200, RBR750, RBK852)Affected if Model is one of: Rax200, Rax80, Rax75, Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, or Rbs850
-
Check installed firmware versionLog into the web management interface and navigate to Administration > Firmware Update or System > Router Information to view the current firmware version numberAffected if Firmware version is below 1.0.3.106 for Rax200/Rax80/Rax75, below 3.2.16.6 for Rbr750/Rbs750/Rbk852/Rbr850, or ANY version for Rbk752 (all versions affected)
-
Verify web management interface is enabledConfirm the router web management interface is accessible from LAN or WAN by attempting to reach the router IP in a browser (typically 192.168.1.1 or 192.168.1.254). Check Administration > Remote Management to see if remote management is enabled.Affected if Web management interface is accessible and attacker can obtain valid authentication credentials
-
Confirm authentication capabilityDetermine if you have valid administrator credentials for the router, or assess whether credentials could be obtained by another party (shared passwords, default credentials, or vulnerability to credential theft)Affected if An attacker can obtain valid authenticated access to the web management interface
You are affected if your router model is one of the listed models, your firmware version is below the specified thresholds (or any version for Rbk752), and an attacker can authenticate to the web management interface.
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.3.1063.2.16.6
Update firmware to version 1.0.3.106 or later for RAX200/RAX75/RAX80 models, and version 3.2.16.6 or later for RBK752/RBR750/RBS750/RBK852/RBR850/RBS850 models.
Firmware 1.0.3.106 for RAX200/RAX80/RAX75 or Firmware 3.2.16.6 for RBK752/RBR750/RBS750/RBK852/RBR850/RBS850
- Identify the exact NETGEAR device model (e.g., RAX200, RAX80, RAX75, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
- Navigate to the NETGEAR support page at kb.netgear.com and search for the device model
- Download the firmware version 1.0.3.106 for RAX200, RAX80, or RAX75 devices
- Download the firmware version 3.2.16.6 for RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 devices
- Access the router's web administration interface (typically at 192.168.1.1)
- Navigate to the Administration or Settings section and locate the Firmware Update option
- Upload and apply the downloaded firmware file
- Allow the device to reboot and complete the update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45537 — 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-45537 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