dbcve.org
Nms300 FirmwareOperating system · Netgear

CVE-2020-35780

MEDIUM · 6.5 CVSS v3.1 Published 2020-12-30
Fix available
A fix is available. Upgrade to 1.6.0.27 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
NETGEAR NMS300 devices before 1.6.0.27 are affected by denial of service.

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 · low confidence

NETGEAR NMS300 (Network Management System 300) devices running firmware versions prior to 1.6.0.27 contain a denial of service vulnerability. The specific vulnerability details and exploitation method are not disclosed in the available advisory.

MitigationUpgrade NETGEAR NMS300 devices to firmware version 1.6.0.27 or later to remediate this vulnerability.

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
Nms300 FirmwareOperating system
Affected:< 1.6.0.27

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NETGEAR NMS300 devices on the network
    Review network inventory or scan for devices responding with NETGEAR NMS300 service signatures (typically HTTP/HTTPS management interface on port 8080/8443 or legacy ports)
    Affected if A device is confirmed to be a NETGEAR NMS300 Network Management System
  2. Locate the firmware version through the management interface
    Log into the NMS300 web console as administrator and navigate to System > About, System > Maintenance > Firmware, or similar status/diagnostics page. The firmware version is usually displayed on the main dashboard or in the device status section
    Affected if The displayed firmware version is visible and is below 1.6.0.27
  3. Check firmware version via CLI if available
    Access the device console (serial, SSH, or telnet) and run commands such as 'show version', 'get firmware version', or 'system info' to retrieve the installed firmware version
    Affected if The command output shows a version number lower than 1.6.0.27
  4. Cross-reference with NETGEAR support portals
    If version information is obtained, compare it against the official NETGEAR firmware changelog or download page for NMS300 to confirm the exact version number and whether it precedes 1.6.0.27
    Affected if The confirmed installed version is less than 1.6.0.27

The environment is affected if any NETGEAR NMS300 device is found running firmware version 1.6.0.26 or earlier.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.6.0.27 or later
Fixed in 1.6.0.27
Interim mitigation

Upgrade NETGEAR NMS300 devices to firmware version 1.6.0.27 or later to remediate this vulnerability.

Fix this in Nms300 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-35780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-35780 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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