CVE-2021-45650
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 disclosure of sensitive information. This affects R7000 before 1.0.11.110, R7900 before 1.0.4.30, R8000 before 1.0.4.62, RS400 before 1.5.1.80, R6400v2 before 1.0.4.102, R7000P before 1.3.2.126, R6700v3 before 1.0.4.102, and R6900P before 1.3.2.126.
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 analysisThe application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.
General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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.11.110< 1.0.4.30< 1.0.4.62< 1.5.1.80< 1.0.4.102< 1.3.2.126< 1.0.4.102< 1.3.2.126CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.4.301.0.4.621.0.4.102
Router-specific firmware: R7000 (1.0.11.110+), R7900 (1.0.4.30+), R8000 (1.0.4.62+), RS400 (1.5.1.80+), R6400v2 (1.0.4.102+), R7000p (1.3.2.126+), R6700v3 (1.0.4.102+), R6900P (1.3.2.126+)
- 1. Identify your specific NETGEAR router model from the affected list (R7000, R7900, R8000, RS400, R6400v2, R7000p, R6700v3, or R6900p)
- 2. Visit the NETGEAR support website and navigate to the firmware download page for your specific router model
- 3. Download the latest firmware version that is equal to or higher than the fixed version for your model: R7000 (1.0.11.110), R7900 (1.0.4.30), R8000 (1.0.4.62), RS400 (1.5.1.80), R6400v2 (1.0.4.102), R7000p (1.3.2.126), R6700v3 (1.0.4.102), or R6900P (1.3.2.126)
- 4. Access your router's web management interface by entering the router's IP address in a web browser
- 5. Navigate to the Administration or Advanced settings section
- 6. Locate the Firmware Update option (often under Advanced > Administration > Router Update)
- 7. Click Browse or Choose File and select the downloaded firmware file
- 8. Click Upload or Update to begin the firmware upgrade process
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45650 — 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-45650 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