CVE-2020-14428
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 administrative credentials. This affects RBK752 before 3.2.15.25, RBK753 before 3.2.15.25, RBK753S before 3.2.15.25, RBR750 before 3.2.15.25, RBS750 before 3.2.15.25, RBK842 before 3.2.15.25, RBR840 before 3.2.15.25, RBS840 before 3.2.15.25, RBK852 before 3.2.15.25, RBK853 before 3.2.15.25, RBR850 before 3.2.15.25, and RBS850 before 3.2.15.25.
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 confidenceMultiple NETGEAR Orbi mesh WiFi systems (RBK752, RBK753, RBK753S, RBR750, RBS750, RBK842, RBR840, RBS840, RBK852, RBK853, RBR850, RBS850) contain a vulnerability allowing disclosure of administrative credentials. An unauthenticated or authenticated attacker could exploit this to gain full administrative access to affected devices.
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< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25CVSS 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 your Orbi device modelLog into the Orbi web interface (typically at 192.168.1.1) or use the Orbi mobile app. Navigate to Settings > About or Administration > Router Status to view the model number (e.g., RBK752, RBR750, etc.).Affected if Your model is one of: RBK752, RBK753, RBR750, RBS750, RBK842, RBR840, RBS840 (or related variants like RBK753S) and the firmware version is below 3.2.15.25.
-
Check the installed firmware versionIn the Orbi web interface, go to Administration > Router/Firmware Update or Settings > About. The current firmware version is displayed (format: x.x.x.x). Note that Satellites will show their own firmware version separately.Affected if The displayed firmware version is lower than 3.2.15.25.
-
Verify both router and satellite firmware versionsIf using a mesh system, check the firmware version for each satellite unit. In the web interface, look for a connected devices list or satellite status page. Each satellite must also be running firmware 3.2.15.25 or later.Affected if Any device in the mesh system (router or satellite) is running firmware below 3.2.15.25.
You are affected if your Orbi router or any satellite is running firmware version lower than 3.2.15.25 on a vulnerable model (RBK752, RBK753, RBK753S, RBR750, RBS750, RBK842, RBR840, RBS840 or related variants).
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.
From vendor data3.2.15.25
Update the firmware on affected NETGEAR Orbi devices to version 3.2.15.25 or later to remediate the credential disclosure vulnerability. After updating, change all administrative credentials as a precaution.
- 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-2020-14428 — 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-2020-14428 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