CVE-2021-45515
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 denial of service. This affects EX7500 before 1.0.0.72, RBS40V before 2.6.1.4, RBW30 before 2.6.1.4, RBRE960 before 6.0.3.68, RBSE960 before 6.0.3.68, RBR750 before 3.2.17.12, RBR850 before 3.2.17.12, RBS750 before 3.2.17.12, RBS850 before 3.2.17.12, RBK752 before 3.2.17.12, and RBK852 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 · moderate confidenceA denial of service vulnerability exists in multiple NETGEAR mesh and router devices (EX7500, RBS40V, RBW30, RBRE960, RBSE960, RBR750, RBR850, SBS750, SBS850, RBK752, RBK852). The specific attack vector and vulnerable component are not detailed in the available information, but exploitation allows remote attackers to cause device unavailability.
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.0.72< 2.6.1.4< 2.6.1.4< 6.0.3.68< 6.0.3.68< 6.0.3.68< 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 modelLocate the device label on the physical device or check the admin web interface (typically at 192.168.1.1) under the firmware or status page to confirm the exact model number (EX7500, RBS40V, RBW30, RBKE963, RBRE960, RBSE960, RBR750, RBR850, or related mesh variants)Affected if The device model is one of: EX7500, RBS40V, RBW30, RBKE963, RBRE960, RBSE960, RBR750, RBR850, or related SBS/RBK models
-
Retrieve the installed firmware versionAccess the router/mmesh admin interface and navigate to the Firmware Update or Status section to view the current firmware version, or use the NETGEAR Nighthawk/Orbi mobile app, or log into the device via SSH/Telnet and run the command to display firmware version (such as 'version' or '固件版本' depending on model)Affected if Unable to retrieve a firmware version from the device because it is unreachable or inaccessible
-
Compare firmware version against affected thresholdsMatch your device model to its corresponding version threshold and verify: EX7500 must be < 1.0.0.72, RBS40V/RBW30 must be < 2.6.1.4, RBKE963/RBRE960/RBSE960 must be < 6.0.3.68, RBR750/RBR850 must be < 3.2.17.12Affected if The installed firmware version is lower than the threshold for your specific model (meaning version number is less than the safe version)
Your device is affected if it is one of the listed NETGEAR models AND its current firmware version falls below the safe version threshold for that model.
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.0.722.6.1.43.2.17.12
Update affected NETGEAR devices to the latest firmware versions: EX7500 to 1.0.0.72+, RBS40V/RBW30 to 2.6.1.4+, RBRE960/RBSE960 to 6.0.3.68+, and RBR750/RBR850/SBS750/SBS850/RBK752/RBK852 to 3.2.17.12+.
EX7500: 1.0.0.72 | RBS40V/RBW30: 2.6.1.4 | RBKE963/RBRE960/RBSE960: 6.0.3.68 | RBR750/RBR850/RBS750/RBS850/RBK752/RBK852: 3.2.17.12
- 1. Identify the specific NETGEAR device model from the affected list (EX7500, RBS40V, RBW30, RBKE963, RBRE960, RBSE960, RBR750, RBR850, RBS750, RBS850, RBK752, RBK852)
- 2. Download the latest firmware version from NETGEAR's support website (kb.netgear.com) for your specific device model
- 3. Ensure the device has stable power during firmware update to prevent brick
- 4. Access the device's web interface or NETGEAR Nighthawk/Orbi app
- 5. Navigate to the firmware update section (typically under Administration > Firmware Update)
- 6. Upload the downloaded firmware file and initiate the update
- 7. Wait for the device to complete the update and reboot automatically
- 8. Verify the firmware version has been updated to the fixed release
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-45515 — 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-45515 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