R6700 FirmwareOperating system · Netgear

CVE-2020-15635

HIGH · 8.8 CVSS v3.1 Published 2020-08-20
Fix available
A fix is available. Upgrade to 1.0.4.98 or later.
See remediation →
93/100
Remediation priority · Urgent
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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700 V1.0.4.84_10.0.58 routers with firmware 1.0.4.84_10.0.58. Authentication is not required to exploit this vulnerability. The specific flaw exists within the acsd service, which listens on TCP port 5916 by default. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the admin user. Was ZDI-CAN-9853.

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 stack-based buffer overflow vulnerability in the acsd service (TCP port 5916) of NETGEAR R6700 routers allows remote attackers to execute arbitrary code without authentication. The flaw stems from insufficient validation of user-supplied data length before copying into a fixed-size stack buffer, enabling code execution in the admin user context.

MitigationApply the latest NETGEAR firmware update for the R6700 model. If no update is available, block TCP port 5916 at the network perimeter or disable the acsd service via router administration.

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
R6700 FirmwareOperating system
Affected:< 1.0.4.98

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
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 checks

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

  1. Confirm router model is R6700
    Access the router administration web interface (typically at 192.168.1.1) and navigate to the Status or Administration page to identify the device model, or inspect the physical device label
    Affected if The device is a NETGEAR R6700 router (other models are not affected by this specific CVE)
  2. Check firmware version
    In the router admin panel, locate the firmware version displayed on the Status or Administration page
    Affected if The installed firmware version is lower than 1.0.4.98 (versions 1.0.4.98 and higher contain the fix)
  3. Verify acsd service is running
    Scan the router from the LAN or WAN interface using a port scanner targeting TCP port 5916 (e.g., nmap -p 5916 <router_ip>), or check running services via telnet/SSH if enabled
    Affected if TCP port 5916 is open and responding on the router
  4. Check network exposure of port 5916
    Determine if port 5916 is accessible from the WAN/internet by scanning the router's public IP address, or review the router firewall settings in the admin panel under Port Forwarding/Port Triggering or Security settings
    Affected if Port 5916 is accessible from an untrusted network (internet or untrusted LAN segment)

The router is affected if it is a NETGEAR R6700 running firmware version below 1.0.4.98 AND the acsd service on TCP port 5916 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.

From vendor data
Upgrade available Upgrade to 1.0.4.98 or later
Fixed in 1.0.4.98
Interim mitigation

Apply the latest NETGEAR firmware update for the R6700 model. If no update is available, block TCP port 5916 at the network perimeter or disable the acsd service via router administration.

Fix this in R6700 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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