CVE-2021-45599
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, 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 confidenceCommand injection vulnerability in NETGEAR CBR40, CBR750, RBK852, RBR850, and RBS850 devices allows authenticated users to execute arbitrary OS commands due to improper input validation in the firmware.
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 your Netgear device modelCheck the device label on the router or satellite unit, or log into the web admin interface and look for the model number displayed on the dashboard or status pageAffected if The model is not one of CBR40, CBR750, RBK852, RBR850, or RBS850 - you are not affected by this specific CVE
-
Check the installed firmware versionLog into the router web admin interface (typically at 192.168.1.1), navigate to Settings > Administration > Firmware Update, or check the status/dashboard page for the current firmware version numberAffected if Unable to determine the firmware version from the admin interface - manual firmware inspection may be required
-
Compare firmware version against affected rangesMatch your installed firmware version to the following vulnerable ranges: CBR40 < 2.5.0.24, CBR750 < 4.6.3.6, RBK852/RBR850/RBS850 < 3.2.17.12Affected if Your firmware version falls within any of these ranges: CBR40 version is below 2.5.0.24, CBR750 version is below 4.6.3.6, or RBK852/RBR850/RBS850 version is below 3.2.17.12 - you are likely affected
-
Verify authentication is enabledConfirm that administrator credentials are set on the device and that the web admin interface requires loginAffected if The device has no administrator password set - the vulnerability requires authenticated access, though an attacker could potentially obtain credentials through other means
You are affected if your device is a Netgear CBR40, CBR750, RBK852, RBR850, or RBS850 running firmware versions below 2.5.0.24, 4.6.3.6, or 3.2.17.12 respectively, and the device has authentication enabled.
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
Upgrade firmware to versions 2.5.0.24 (CBR40), 4.6.3.6 (CBR750), or 3.2.17.12 (RBK852/RBR850/RBS850) to patch the vulnerability.
CBR40: 2.5.0.24 | CBR750: 4.6.3.6 | RBK852/RBR850/RBS850: 3.2.17.12
- Log in to the NETGEAR router web interface (typically at routerlogin.net or routerlogin.com)
- Navigate to the Administration or Settings section
- Look for Firmware Update or Router Update option
- Check for available updates - the router should detect and offer the fixed version
- Alternatively, manually download the firmware from the NETGEAR support site (kb.netgear.com) for your specific model
- If manually updating, select the appropriate firmware file for your device model and version
- Upload the firmware file and wait for the update to complete - do not power off the device during this process
- After the update completes, verify the firmware version matches the fixed release (CBR40: 2.5.0.24, CBR750: 4.6.3.6, RBK852/RBR850/RBS850: 3.2.17.12)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45599 — 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-45599 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