R7800 FirmwareOperating system · Netgear

CVE-2020-11790

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 1.0.2.68 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
NETGEAR R7800 devices before 1.0.2.68 are affected by remote code execution by unauthenticated attackers.

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

NETGEAR R7800 firmware before version 1.0.2.68 contains a critical vulnerability allowing unauthenticated remote attackers to execute arbitrary code on the affected device.

MitigationUpdate NETGEAR R7800 firmware to version 1.0.2.68 or later to remediate the 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
R7800 FirmwareOperating system
Affected:< 1.0.2.68

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. Confirm device model is Netgear R7800
    Access the router admin web interface at the default gateway (typically 192.168.1.1) and verify the model number in the web interface, or check the physical device label on the router chassis.
    Affected if The device is not a Netgear R7800 router.
  2. Check installed firmware version
    In the router web interface, navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version. Alternatively, access the router via SSH or telnet if enabled and run the command 'nvram get firmware_version' or check the version in the system log.
    Affected if The displayed firmware version is earlier than 1.0.2.68.
  3. Verify router is network accessible
    Confirm the router management interface (HTTP/HTTPS on ports 80/443 or telnet/SSH) is reachable from the network. Check if remote management is enabled under Advanced > Administration > Remote Management in the web interface.
    Affected if The router management interface is exposed to untrusted networks and the firmware version is below 1.0.2.68.
  4. Review firmware file header if firmware file is available
    If you have a firmware image file, inspect the file header or use a tool like 'strings' to search for the version string within the binary file.
    Affected if The firmware file version string indicates a version lower than 1.0.2.68.

The device is affected if it is a Netgear R7800 router running firmware version earlier than 1.0.2.68 and the router management interface is accessible to the attacker.

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.2.68 or later
Fixed in 1.0.2.68
Interim mitigation

Update NETGEAR R7800 firmware to version 1.0.2.68 or later to remediate the vulnerability.

Recommended fix High confidence

R7800 Firmware version 1.0.2.68 or later

  1. Download firmware version 1.0.2.68 or later for the R7800 from the official NETGEAR support site (kb.netgear.com)
  2. Access the R7800 router's web management interface by entering the router's IP address in a web browser
  3. Log into the router administration panel with administrator credentials
  4. Navigate to the 'Advanced' or 'Administration' section and select 'Firmware Update' or 'Router Update'
  5. Click 'Choose File' and select the downloaded firmware file (.img)
  6. Click 'Upload' or 'Update' to begin the firmware upgrade process
  7. Wait for the upgrade to complete - do not power off the router during this process
  8. After the router restarts, verify the firmware version is 1.0.2.68 or later in the web interface
Caveat Firmware upgrades carry inherent risk; ensure stable power during upload; some settings may reset to defaults

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

Fix this in R7800 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11790 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