CVE-2021-45573
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 a stack-based buffer overflow by an unauthenticated attacker. This affects R6260 before 1.1.0.76, R6800 before 1.2.0.62, R6700v2 before 1.2.0.62, R6900v2 before 1.2.0.62, R7450 before 1.2.0.62, AC2100 before 1.2.0.62, AC2400 before 1.2.0.62, and AC2600 before 1.2.0.62.
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 confidenceA stack-based buffer overflow vulnerability exists in the web interface of multiple NETGEAR router models (R6260, R6800, R6700v2, R6900v2, R7450, AC2100, AC2400, AC2600). An unauthenticated remote attacker can exploit this to execute arbitrary code or cause denial of service, as indicated by the HIGH CVSS score of 8.8.
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.1.0.76< 1.2.0.62< 1.2.0.62< 1.2.0.62< 1.2.0.62< 1.2.0.62< 1.2.0.62< 1.2.0.62CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 modelCheck the physical router label or log into the web interface to confirm the exact model number (R6260, R6800, R6700, R6900, R7450, AC2100, AC2400, or AC2600)Affected if Router model is one of the eight affected models listed in the CVE
-
Check installed firmware versionLog into the router web interface and navigate to the Administration or Firmware Update section to view the current firmware version, or use the router's diagnostic page (often at http://routerlogin.net or 192.168.1.1)Affected if Firmware version is below 1.1.0.76 for R6260, or below 1.2.0.62 for R6800/R6700/R6900/R7450/AC2100/AC2400/AC2600
-
Verify web management interface accessibilityConfirm whether the router's web interface is accessible from external networks by checking the remote management settings (typically under Advanced > Administration > Remote Management) or by attempting to access the router's public IP on ports 80/443Affected if Remote web management is enabled and the router is directly exposed to the internet or untrusted networks
-
Confirm vulnerability trigger conditionThe flaw exists in the web interface component. Check if the HTTP/HTTPS service is running on the router by accessing the login page from both LAN and WAN interfacesAffected if The web interface service is active and reachable, which is required for the buffer overflow to be exploitable
The router is affected if it is one of the eight listed models running firmware below the specified version thresholds AND its web interface is accessible (particularly from WAN for remote exploitation).
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.1.0.761.2.0.62
Update firmware to the patched versions: R6260 to 1.1.0.76, and R6800/R6700v2/R6900v2/R7450/AC2100/AC2400/AC2600 to 1.2.0.62. If patching is not immediately possible, restrict web management interface access to trusted networks or disable remote management.
R6260: upgrade to firmware 1.1.0.76 | R6800, R6700v2, R6900v2, R7450, AC2100, AC2400, AC2600: upgrade to firmware 1.2.0.62
- 1. Identify your NETGEAR router model from the affected list (R6260, R6800, R6700v2, R6900v2, R7450, AC2100, AC2400, or AC2600)
- 2. Access the router's web interface by entering the router's IP address in a web browser (commonly 192.168.1.1 or 192.168.0.1)
- 3. Log in with your router administrator credentials
- 4. Navigate to the 'Administration' or 'Advanced' settings section
- 5. Locate the 'Firmware Update' or 'Router Update' option
- 6. Check the current firmware version under 'Current Version' or similar field
- 7. If the version is below the fixed release (R6260: < 1.1.0.76, all others: < 1.2.0.62), download the correct firmware from the official NETGEAR support site (kb.netgear.com)
- 8. In the router's firmware update page, select 'Upload' or 'Browse' to select the downloaded firmware file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45573 — 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-45573 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