dbcve.org
R6700 FirmwareOperating system · Netgear

CVE-2020-10930

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 disclose sensitive information on affected installations of NETGEAR R6700 V1.0.4.84_10.0.58 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of URLs. The issue results from the lack of proper routing of URLs. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-9618.

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

This is an information disclosure vulnerability in NETGEAR R6700 routers (firmware V1.0.4.84_10.0.58) where improper URL routing allows unauthenticated, network-adjacent attackers to access stored credentials. The lack of proper routing logic in the web interface enables direct access to sensitive authentication data without any credentials.

MitigationApply the vendor-supplied firmware update when available; until then, restrict network access to the router management interface via network segmentation or firewall rules, and change exposed credentials.

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.84_10.0.58

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
None
Availability
None

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

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 NETGEAR R6700
    Check the device label on the router physical case, or log into the router web interface and look for the model number in the admin panel (typically under Administration > Router Status or similar).
    Affected if The device model is not NETGEAR R6700, then this specific CVE does not apply.
  2. Identify installed firmware version
    Log into the router web interface and navigate to Administration > Firmware Update or Router Status page. The firmware version is displayed there. Alternatively, check the download file name if you updated firmware from NETGEAR support downloads.
    Affected if The installed firmware version is exactly 1.0.4.84_10.0.58, matching the affected version.
  3. Verify web management interface is network-accessible
    From a computer on the same network (but not the router itself), open a web browser and navigate to the router's LAN IP address (commonly 192.168.1.1). If the login page loads without requiring VPN or local-only access, the interface is network-adjacent accessible.
    Affected if The router web interface is accessible from a network-adjacent host without special network segmentation.
  4. Check for credential exposure via URL
    This vulnerability involves improper URL routing that allows unauthenticated access to stored credentials. If you suspect exposure, inspect any unusual URLs or endpoints in the router's web interface that may return authentication data without login.
    Affected if Network-adjacent unauthenticated attackers can retrieve stored credentials through direct URL access, which indicates exploitation of this vulnerability.

You are affected if you have a NETGEAR R6700 router running firmware version 1.0.4.84_10.0.58 with its web management interface accessible to network-adjacent attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update when available; until then, restrict network access to the router management interface via network segmentation or firewall rules, and change exposed credentials.

Fix this in R6700 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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