CVE-2020-14442
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 unauthenticated attacker. 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 (RBK/RBR/RBS series) contain a command injection vulnerability allowing unauthenticated attackers to execute arbitrary commands on the underlying operating system due to insufficient input sanitization 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< 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 the Orbi device modelLocate the model number on the device label or check via the web interface at orbilogin.com under Administration > Device Information. Confirm the model matches one of the affected series: RBK752, RBK753, RBK753S, RBR750, RBS750, RBK842, RBR840, or RBS840.Affected if The device model is any of the RBK/RBR/RBS series listed in the affected products.
-
Check the installed firmware versionAccess the Orbi web interface at orbilogin.com, navigate to Administration > Firmware Update or Device Information, and note the current firmware version displayed.Affected if The firmware version is lower than 3.2.15.25 (for example, 3.2.14.x or earlier).
-
Verify management interface exposureCheck if the Orbi web management interface (port 80/443 on orbilogin.com or the device IP) is accessible from the internet or an untrusted network segment.Affected if The management interface is exposed to untrusted networks without firewall restrictions.
-
Look for unexpected processes or configurationsIf telnet or SSH access is enabled on the device, connect and review running processes with 'ps' and check for unexpected cron jobs or scripts in /tmp or /var directories.Affected if Unexpected scripts, unknown processes, or modified configurations are found on the device.
A user is affected if their Orbi device is one of the listed models (RBK/RBR/RBS series) and is running firmware version lower than 3.2.15.25 with its management interface accessible to attackers.
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 all affected NETGEAR devices to firmware version 3.2.15.25 or later. If immediate patching is not possible, restrict network access to management interfaces and monitor for suspicious activity.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14442 — 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-14442 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