dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2020-35796

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-30
Fix available
A fix is available. Upgrade to 1.0.0.36 / 1.0.0.48 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 a buffer overflow by an unauthenticated attacker. This affects CBR40 before 2.5.0.10, D6220 before 1.0.0.60, D6400 before 1.0.0.94, D7000v2 before 1.0.0.62, D8500 before 1.0.3.50, DC112A before 1.0.0.48, DGN2200v4 before 1.0.0.114, EAX20 before 1.0.0.36, EAX80 before 1.0.1.62, EX3700 before 1.0.0.84, EX3800 before 1.0.0.84, EX3920 before 1.0.0.84, EX6000 before 1.0.0.44, EX6100 before 1.0.2.28, EX6120 before 1.0.0.54, EX6130 before 1.0.0.36, EX6150 before 1.0.0.46, EX6200 before 1.0.3.94, EX6920 before 1.0.0.54, EX7000 before 1.0.1.90, EX7500 before 1.0.0.68, MK62 before 1.0.5.102, MR60 before 1.0.5.102, MS60 before 1.0.5.102, R6250 before 1.0.4.42, R6300v2 before 1.0.4.42, R6400 before 1.0.1.62, R6400v2 before 1.0.4.98, R6700v3 before 1.0.4.98, R6700 before 1.0.2.16, R6900P before 1.3.2.124, R6900 before 1.0.2.16, R7000 before 1.0.11.106, R7000P before 1.3.2.124, R7100LG before 1.0.0.56, 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, RAX15 before 1.0.1.64, RAX20 before 1.0.1.64, RAX200 before 1.0.2.102, RAX45 before 1.0.2.32, RAX50 before 1.0.2.32, RAX75 before 1.0.3.102, RAX80 before 1.0.3.102, 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-200 before 1.0.0.46, RBW30 before 2.5.0.4, RS400 before 1.5.0.48, WN2500RPv2 before 1.0.1.56, WN3500RP before 1.0.0.28, WNDR3400v3 before 1.0.1.32, WNR1000v3 before 1.0.2.78, WNR2000v2 before 1.2.0.12, WNR3500Lv2 before 1.2.0.62, and XR300 before 1.0.3.50.

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 confidence

A critical buffer overflow vulnerability in NETGEAR router and range extender firmware allows unauthenticated remote attackers to execute arbitrary code by overflowing a memory buffer. The vulnerability affects over 70 different NETGEAR device models, each with a specific firmware version threshold before which they are vulnerable.

MitigationUpdate affected NETGEAR devices to the firmware versions specified in the advisory (e.g., R7000 to 1.0.11.106, R6400 to 1.0.1.62) or later to remediate the buffer overflow 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
Cbr40 FirmwareOperating system
Affected:< 2.5.0.10
D6220 FirmwareOperating system
Affected:< 1.0.0.60
D6400 FirmwareOperating system
Affected:< 1.0.0.94
D7000v2 FirmwareOperating system
Affected:< 1.0.0.62
D8500 FirmwareOperating system
Affected:< 1.0.3.50
Dc112a FirmwareOperating system
Affected:< 1.0.0.48
Dgn2200v4 FirmwareOperating system
Affected:< 1.0.0.114
Eax20 FirmwareOperating system
Affected:< 1.0.0.36

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
High

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

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

  1. Identify the NETGEAR device model
    Locate the model number on the device label (usually on the bottom or back of the router) or check the device information page in the router's web administration interface under 'Router Info' or 'Device Status'
    Affected if The model matches one of: Cbr40, D6220, D6400, D7000v2, D8500, Dc112a, Dgn2200v4, or Eax20
  2. Locate the firmware version in the admin interface
    Log into the router's web interface (typically at 192.168.1.1 or 192.168.0.1) and navigate to 'Advanced' > 'Administration' > 'Router Update' or 'Device Status' to view the current firmware version
    Affected if The firmware version cannot be determined or the page is inaccessible
  3. Compare your firmware version against the affected threshold
    Take the firmware version shown in the admin interface (for example, 2.3.1.26) and compare it numerically to the threshold for your specific model: Cbr40 < 2.5.0.10, D6220 < 1.0.0.60, D6400 < 1.0.0.94, D7000v2 < 1.0.0.62, D8500 < 1.0.3.50, Dc112a < 1.0.0.48, Dgn2200v4 < 1.0.0.114, Eax20 < 1.0.0.36
    Affected if The installed version is lower than the threshold for your device model (versions are compared as numerical tuples, e.g., 1.0.0.50 is older than 1.0.0.60)

You are affected if you own one of the listed NETGEAR models and your installed firmware version is lower than the specified threshold for that model.

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.36 / 1.0.0.48 / 1.0.0.60 or later
Fixed in 1.0.0.361.0.0.481.0.0.60
Interim mitigation

Update affected NETGEAR devices to the firmware versions specified in the advisory (e.g., R7000 to 1.0.11.106, R6400 to 1.0.1.62) or later to remediate the buffer overflow vulnerability.

Recommended fix High confidence

Minimum fixed firmware versions: CBR40: 2.5.0.10, D6220: 1.0.0.60, D6400: 1.0.0.94, D7000v2: 1.0.0.62, D8500: 1.0.3.50, DC112A: 1.0.0.48, DGN2200v4: 1.0.0.114, EAX20: 1.0.0.36 (or later)

  1. 1. Identify your specific NETGEAR device model from the affected list (CBR40, D6220, D6400, D7000v2, D8500, DC112A, DGN2200v4, or EAX20).
  2. 2. Access the device web interface or NETGEAR Nighthawk/Orbi app to check the current firmware version.
  3. 3. Navigate to the NETGEAR support page (kb.netgear.com) and locate the firmware download page for your specific device model.
  4. 4. Download the firmware version equal to or newer than the minimum fixed version for your device: CBR40: 2.5.0.10, D6220: 1.0.0.60, D6400: 1.0.0.94, D7000v2: 1.0.0.62, D8500: 1.0.3.50, DC112A: 1.0.0.48, DGN2200v4: 1.0.0.114, EAX20: 1.0.0.36.
  5. 5. In the device web interface, go to Administration > Firmware Update or similar section.
  6. 6. Upload the downloaded firmware file and allow the device to complete the update process (do not power off during update).
  7. 7. After reboot, verify the firmware version has been updated successfully.
Caveat Firmware updates may reset device configurations; back up settings before updating if possible

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

Fix this in Cbr40 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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