dbcve.org
D7800 FirmwareOperating system · Netgear

CVE-2017-18751

HIGH · 8.8 CVSS v3.1 Published 2020-04-23
Fix available
A fix is available. Upgrade to 1.0.0.48 / 1.0.0.112 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
Certain NETGEAR devices are affected by a stack-based buffer overflow by an unauthenticated attacker. This affects D7800 before 1.0.1.28, R6100 before 1.0.1.16, R7500 before 1.0.0.112, R7500v2 before 1.0.3.20, R7800 before 1.0.2.36, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.88, WNDR4300 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, and WNDR4500v3 before 1.0.0.48.

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

Stack-based buffer overflow in NETGEAR router firmware (multiple models including D7800, R6100, R7500, R7800, R9000, and WNDR series) exploitable by unauthenticated attackers via malformed input. The vulnerability allows remote code execution or device compromise without requiring prior authentication.

MitigationUpdate affected NETGEAR devices to the specified firmware versions: D7800 to 1.0.1.28, R6100 to 1.0.1.16, R7500 to 1.0.0.112, R7500v2 to 1.0.3.20, R7800 to 1.0.2.36, R9000 to 1.0.2.52, WNDR3700v4 to 1.0.2.88, WNDR4300 to 1.0.2.90, WNDR4300v2 to 1.0.0.48, and WNDR4500v3 to 1.0.0.48.

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
D7800 FirmwareOperating system
Affected:< 1.0.1.28
R6100 FirmwareOperating system
Affected:< 1.0.1.16
R7500 FirmwareOperating system
Affected:< 1.0.0.112< 1.0.3.20
R7800 FirmwareOperating system
Affected:< 1.0.2.36
R9000 FirmwareOperating system
Affected:< 1.0.2.52
Wndr3700 FirmwareOperating system
Affected:< 1.0.2.88
Wndr4300 FirmwareOperating system
Affected:< 1.0.2.90< 1.0.0.48
Wndr4500 FirmwareOperating system
Affected:< 1.0.0.48

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. Identify your NETGEAR device model
    Log into the router web interface (typically http://192.168.1.1) and check the status or device info page to find the exact model number (such as D7800, R6100, R7500, R7800, R9000, WNDR3700, WNDR4300, or WNDR4500)
    Affected if The device model matches one of the affected models listed in the CVE (D7800, R6100, R7500, R7800, R9000, or WNDR series)
  2. Locate the firmware version
    In the router web interface, navigate to the Administration or Router Status page to find the installed firmware version number
    Affected if A firmware version is displayed on the device (proceed to version comparison)
  3. Compare your D7800 firmware version
    If your device is a D7800, compare your installed version against 1.0.1.28. Versions below 1.0.1.28 are affected
    Affected if Installed version is lower than 1.0.1.28
  4. Compare your R6100 firmware version
    If your device is an R6100, compare your installed version against 1.0.1.16. Versions below 1.0.1.16 are affected
    Affected if Installed version is lower than 1.0.1.16
  5. Compare your R7500 firmware version
    If your device is an R7500, compare your installed version against both 1.0.0.112 and 1.0.3.20. Versions below either threshold are affected (check both as there are two version branches)
    Affected if Installed version is lower than 1.0.0.112 OR lower than 1.0.3.20
  6. Compare your R7800, R9000, or WNDR firmware version
    For R7800 compare against 1.0.2.36, for R9000 compare against 1.0.2.52, for WNDR3700 compare against 1.0.2.88, for WNDR4300 compare against 1.0.2.90 and 1.0.0.48, for WNDR4500 compare against 1.0.0.48. Versions below any applicable threshold are affected
    Affected if Installed version is lower than the applicable threshold for your specific model

You are affected if you own one of the listed NETGEAR models and your installed firmware version falls below the specified version 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.

From vendor data
Upgrade available Upgrade to 1.0.0.48 / 1.0.0.112 / 1.0.1.16 or later
Fixed in 1.0.0.481.0.0.1121.0.1.16
Interim mitigation

Update affected NETGEAR devices to the specified firmware versions: D7800 to 1.0.1.28, R6100 to 1.0.1.16, R7500 to 1.0.0.112, R7500v2 to 1.0.3.20, R7800 to 1.0.2.36, R9000 to 1.0.2.52, WNDR3700v4 to 1.0.2.88, WNDR4300 to 1.0.2.90, WNDR4300v2 to 1.0.0.48, and WNDR4500v3 to 1.0.0.48.

Fix this in D7800 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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