dbcve.org
Ac2100 FirmwareOperating system · Netgear

CVE-2020-35800

CRITICAL · 9.4 CVSS v3.1 Published 2020-12-30
Fix available
A fix is available. Upgrade to 1.0.0.60 / 1.0.0.80 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Certain NETGEAR devices are affected by incorrect configuration of security settings. This affects AC2100 before 1.2.0.72, AC2400 before 1.2.0.72, AC2600 before 1.2.0.72, CBK40 before 2.5.0.10, CBR40 before 2.5.0.10, D6000 before 1.0.0.80, D6220 before 1.0.0.60, D6400 before 1.0.0.94, D7000v2 before 1.0.0.62, D7800 before 1.0.3.48, D8500 before 1.0.3.50, DC112A before 1.0.0.48, DGN2200v4 before 1.0.0.114, DM200 before 1.0.0.66, EAX20 before 1.0.0.36, EAX80 before 1.0.1.62, EX2700 before 1.0.1.58, EX3110 before 1.0.1.68, EX3700 before 1.0.0.84, EX3800 before 1.0.0.84, EX3920 before 1.0.0.84, EX6000 before 1.0.0.44, EX6100v2 before 1.0.1.94, EX6110 before 1.0.1.68, EX6120 before 1.0.0.54, EX6130 before 1.0.0.36, EX6150v1 before 1.0.0.46, EX6150v2 before 1.0.1.94, EX6200v1 before 1.0.3.94, EX6250 before 1.0.0.128, EX6400 before 1.0.2.152, EX6400v2 before 1.0.0.128, EX6410 before 1.0.0.128, EX6920 before 1.0.0.54, EX7000 before 1.0.1.90, EX7300 before 1.0.2.152, EX7300v2 before 1.0.0.128, EX7320 before 1.0.0.128, EX7500 before 1.0.0.68, EX7700 before 1.0.0.210, EX8000 before 1.0.1.224, MK62 before 1.0.5.102, MR60 before 1.0.5.102, MS60 before 1.0.5.102, R6120 before 1.0.0.70, R6220 before 1.1.0.100, R6230 before 1.1.0.100, R6250 before 1.0.4.42, R6260 before 1.1.0.76, R6300v2 before 1.0.4.42, R6330 before 1.1.0.76, R6350 before 1.1.0.76, R6400v1 before 1.0.1.62, R6400v2 before 1.0.4.98, R6700v1 before 1.0.2.16, R6700v2 before 1.2.0.72, R6700v3 before 1.0.4.98, R6800 before 1.2.0.72, R6800 before 1.2.0.72, R6850 before 1.1.0.76, R6900 before 1.0.2.16, R6900P before 1.3.2.124, R6900v2 before 1.2.0.72, R7000 before 1.0.11.106, R7000P before 1.3.2.124, R7100LG before 1.0.0.56, R7200 before 1.2.0.72, R7350 before 1.2.0.72, R7400 before 1.2.0.72, R7450 before 1.2.0.72, R7500v2 before 1.0.3.48, R7800 before 1.0.2.74, R7850 before 1.0.5.60, R7900 before 1.0.4.26, R7900P before 1.4.1.62, R7960P before 1.4.1.62, R8000 before 1.0.4.58, R8000P before 1.4.1.62, R8300 before 1.0.2.134, R8500 before 1.0.2.134, R8900 before 1.0.5.24, R9000 before 1.0.5.24, RAX120 before 1.0.1.136, RAX15 before 1.0.1.64, RAX20 before 1.0.1.64, RAX200 before 1.0.5.24, RAX35 before 1.0.3.80, RAX40 before 1.0.3.80, RAX45 before 1.0.2.64, RAX50 before 1.0.2.64, RAX75 before 1.0.3.102, RAX80 before 1.0.3.102, RBK12 before 2.6.1.44, RBR10 before 2.6.1.44, RBS10 before 2.6.1.44, RBK20 before 2.6.1.38, RBR20 before 2.6.1.36, RBS20 before 2.6.1.38, RBK40 before 2.6.1.38, RBR40 before 2.6.1.38, RBS40 before 2.6.1.38, RBK50 before 2.6.1.40, RBR50 before 2.6.1.40, RBS50 before 2.6.1.40, RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK842 before 3.2.16.6, RBR840 before 3.2.16.6, RBS840 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, RBS850 before 3.2.16.6, RBS40V before 2.5.1.6, RBS40V-200 before 1.0.0.46, RBS50Y before 2.6.1.40, RBW30 before 2.5.0.4, RS400 before 1.5.0.48, WN2500RPv2 before 1.0.1.56, WN3000RPv3 before 1.0.2.86, WN3500RPv1 before 1.0.0.28, WNDR3400v3 before 1.0.1.32, WNR1000v3 before 1.0.2.78, WNR2000v2 before 1.2.0.12, XR300 before 1.0.3.50, XR450 before 2.3.2.66, XR500 before 2.3.2.66, and XR700 before 1.0.1.34.

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

Multiple NETGEAR router and mesh system devices contain incorrect security settings in their default configuration. The specific nature of the misconfiguration is not detailed in the advisory, but the CVSS 9.4 score indicates it is exploitable over the network and allows unauthorized access or bypass of security controls.

MitigationApply the firmware updates specified for each device model in the advisory. For devices that cannot be updated, consider network segmentation and disabling unnecessary services.

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
Ac2100 FirmwareOperating system
Affected:< 1.2.0.72
Ac2400 FirmwareOperating system
Affected:< 1.2.0.72
Ac2600 FirmwareOperating system
Affected:< 1.2.0.72
Cbk40 FirmwareOperating system
Affected:< 2.5.0.10
Cbr40 FirmwareOperating system
Affected:< 2.5.0.10
D6000 FirmwareOperating system
Affected:< 1.0.0.80
D6220 FirmwareOperating system
Affected:< 1.0.0.60
D6400 FirmwareOperating system
Affected:< 1.0.0.94

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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 the NETGEAR device model
    Check the device label on the router chassis or log into the router web interface (typically at 192.168.1.1) and view the device information page to confirm the exact model (e.g., Ac2100, Ac2400, Ac2600, Cbk40, Cbr40, D6000, D6220, or D6400)
    Affected if The device model is any of the eight models listed in the affected products list
  2. Determine the installed firmware version
    Log into the router web administration interface and navigate to the Firmware Update or Router Status page. The firmware version is typically displayed as a numeric string (e.g., 1.2.0.72, 2.5.0.10)
    Affected if Unable to retrieve the firmware version through the web interface
  3. Compare firmware version against affected ranges
    For your specific device model, compare your installed firmware version to the affected threshold: Ac2100/Ac2400/Ac2600 < 1.2.0.72, Cbk40/Cbr40 < 2.5.0.10, D6000 < 1.0.0.80, D6220 < 1.0.0.60, D6400 < 1.0.0.94
    Affected if The installed firmware version is lower than the specified threshold for your device model
  4. Verify the default configuration has not been modified
    If possible, review the router security settings in the web interface under Wireless, Administration, or Security settings pages to confirm whether default settings remain unchanged
    Affected if The router still uses factory default settings and the firmware version is in the affected range

You are affected if you are running any of the eight listed NETGEAR device models with a firmware version below the specified threshold for that model, as the default configuration contains the security misconfiguration.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.0.60 / 1.0.0.80 / 1.0.0.94 or later
Fixed in 1.0.0.601.0.0.801.0.0.94
Interim mitigation

Apply the firmware updates specified for each device model in the advisory. For devices that cannot be updated, consider network segmentation and disabling unnecessary services.

Recommended fix High confidence

AC2100/AC2400/AC2600: 1.2.0.72 or later | CBK40/CBR40: 2.5.0.10 or later | D6000: 1.0.0.80 or later | D6220: 1.0.0.60 or later | D6400: 1.0.0.94 or later (and other models to their respective fixed versions as listed in NETGEAR advisory)

  1. Identify the exact model number of your NETGEAR device
  2. Check the current firmware version in the router's web interface under Administration > Firmware Update or similar
  3. Download the latest firmware for your specific model from the official NETGEAR support site (support.netgear.com)
  4. Upload and install the firmware through the router's web interface or NETGEAR Nighthawk/Orbi app
  5. After reboot, verify the firmware version has been updated to the fixed release
  6. Ensure remote management is disabled if not needed, as this was the security misconfiguration
Caveat Review NETGEAR release notes for your specific model; some older hardware may have limited feature support in newer firmware

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ac2100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-35800 — 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-35800 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