CVE-2021-45597
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 CBR40 before 2.5.0.24, CBR750 before 4.6.3.6, RBR850 before 3.2.17.12, RBS850 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 confidenceAuthenticated command injection vulnerability in multiple NETGEAR Orbi router and mesh systems (CBR40, CBR750, RBR850, RBS850). An authenticated attacker can execute arbitrary commands on the device through improper input sanitization 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< 2.5.0.24< 4.6.3.6< 3.2.17.12< 3.2.17.12< 3.2.17.12CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 device modelCheck the device label on the router or mesh satellite, or log into the web management interface and look for the model number displayed on the dashboard or status page.Affected if The device model is CBR40, CBR750, RBR850, RBS850, or RBK852.
-
Determine the installed firmware versionLog into the web management interface (usually at http://192.168.1.1 or http://orbilogin.net), navigate to the Administration or Advanced settings section, and locate the firmware version displayed on the status or diagnostics page.Affected if The firmware version cannot be determined from the web interface.
-
Compare firmware version against affected rangesUsing the identified model and firmware version, compare against these ranges: CBR40 < 2.5.0.24, CBR750 < 4.6.3.6, RBR850/RBS850/RBK852 < 3.2.17.12.Affected if The installed firmware version is lower than the listed fixed version for your model.
-
Verify web management interface accessibilityConfirm whether the administrative web interface is accessible from outside your trusted local network, as the vulnerability requires an authenticated attacker to reach this interface.Affected if The web management interface is exposed to untrusted networks without VPN or IP restriction controls.
You are affected if your device model matches one of the listed products and your current firmware version is below the specified fix for that model and the administrative web interface is reachable by 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 · scoped2.5.0.243.2.17.124.6.3.6
Update affected NETGEAR devices to firmware versions 2.5.0.24 (CBR40), 4.6.3.6 (CBR750), or 3.2.17.12 (RBR850/RBS850) or later. Restrict administrative interface access to trusted networks.
CBR40: 2.5.0.24 | CBR750: 4.6.3.6 | RBR850: 3.2.17.12 | RBS850: 3.2.17.12 | RBK852: 3.2.17.12
- 1. Identify the exact NETGEAR device model from the affected list (CBR40, CBR750, RBR850, RBS850, or RBK852)
- 2. Access the device's web management interface using an authenticated admin account
- 3. Navigate to the firmware update or administration section, typically found under 'Settings' > 'Administration' or 'Firmware Update'
- 4. Check the current firmware version under 'Router Status' or 'Device Information'
- 5. If the current version is below the fixed release (CBR40: < 2.5.0.24, CBR750: < 4.6.3.6, RBR850/RBS850/RBK852: < 3.2.17.12), download the firmware update from the official NETGEAR support site (support.netgear.com or kb.netgear.com)
- 6. In the firmware update section, upload the downloaded firmware file and initiate the update
- 7. Wait for the update process to complete - do not power off the device during the update
- 8. After reboot, verify the new firmware version matches the fixed release or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45597 — 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-45597 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