CVE-2017-6862
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 · uneditedNETGEAR WNR2000v3 devices before 1.1.2.14, WNR2000v4 devices before 1.0.0.66, and WNR2000v5 devices before 1.0.0.42 allow authentication bypass and remote code execution via a buffer overflow that uses a parameter in the administration webapp. The NETGEAR ID is PSV-2016-0261.
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 confidenceNETGEAR WNR2000v3, v4, and v5 wireless routers contain a buffer overflow vulnerability in their administration web interface that allows both authentication bypass and remote code execution. The flaw is triggered via a specific parameter in the webapp, enabling attackers to gain full control of affected devices without valid 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< 1.0.0.42< 1.0.0.66< 1.1.2.14CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR device modelLocate the model number label on the router or access the admin web interface and check the device information page. Look for WNR2000v3, WNR2000v4, or WNR2000v5.Affected if The device is a WNR2000v3, WNR2000v4, or WNR2000v5 model.
-
Determine the installed firmware versionAccess the router admin web interface (typically at 192.168.1.1) and navigate to the Router Status or Administration section to view the firmware version. Alternatively, check the NETGEAR support website using the model number.Affected if The displayed firmware version is below 1.1.2.14 for WNR2000v3, below 1.0.0.66 for WNR2000v4, or below 1.0.0.42 for WNR2000v5.
-
Verify the admin web interface is accessibleAttempt to reach the router web interface from a connected device by navigating to http://192.168.1.1 or the router's LAN IP address in a web browser.Affected if The admin web interface is reachable on the network.
-
Confirm NTP or time settings configurationCheck the router admin interface under Advanced or Administration settings for Network Time Protocol (NTP) configuration. Some exploitation techniques rely on time-based elements.Affected if NTP is enabled and the router synchronizes with external time servers, which may be used as part of the exploitation chain.
If the device is a WNR2000v3, v4, or v5 and the firmware version is below the respective threshold (1.1.2.14, 1.0.0.66, or 1.0.0.42) with the admin interface accessible, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.0.421.0.0.661.1.2.14
Apply the appropriate firmware update (v1.1.2.14 for v3, v1.0.0.66 for v4, or v1.0.0.42 for v5) from NETGEAR's support site to remediate this vulnerability. Until patched, restrict administrative web interface access to trusted networks or disable remote administration.
WNR2000v3: firmware 1.1.2.14; WNR2000v4: firmware 1.0.0.66; WNR2000v5: firmware 1.0.0.42
- 1. Identify the exact model variant (v3, v4, or v5) of the NETGEAR WNR2000 router by checking the device label or web interface.
- 2. Navigate to the official NETGEAR support download page: https://www.netgear.com/support/
- 3. Enter WNR2000 in the search and select the specific model variant.
- 4. Download the firmware version 1.1.2.14 for WNR2000v3, version 1.0.0.66 for WNR2000v4, or version 1.0.0.42 for WNR2000v5.
- 5. Log into the router's web administration interface (typically at 192.168.1.1).
- 6. Navigate to the Administration > Firmware Update or similar section.
- 7. Select the downloaded firmware file and initiate the upgrade. Do not power off the router during the update process.
- 8. After the upgrade completes, verify the firmware version in the router status page to confirm the update was successful.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-6862 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6862 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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