CVE-2018-21140
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 · uneditedCertain NETGEAR devices are affected by incorrect configuration of security settings. This affects D3600 before 1.0.0.76 and D6000 before 1.0.0.76.
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 confidenceCertain NETGEAR D3600 and D6000 router models running firmware versions before 1.0.0.76 contain incorrect security settings configuration, potentially allowing unauthorized access or exposure of sensitive functions.
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.76< 1.0.0.76CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm router modelAccess the router admin web interface (typically at 192.168.1.1) and check the device model under Status or Device Information section. Alternatively, check the product label on the device itself.Affected if Model is NETGEAR D3600 or D6000
-
Check firmware versionIn the router admin interface, navigate to Status or Advanced > Administration > Firmware Update to view the current firmware version number.Affected if Firmware version is less than 1.0.0.76 (for example, 1.0.0.75, 1.0.0.70, etc.)
-
Verify remote management exposureFrom a device on the WAN (outside) network, attempt to access the router login page using the public IP address. Check if the web management interface is reachable from the internet. Also scan the WAN IP for open ports like 80, 443, 8080, or 8443 using a port scanner.Affected if Router admin interface is accessible from WAN side without VPN or port forwarding restriction
-
Check for unnecessary servicesUse the router admin interface to review enabled features under Advanced settings. Look for features like Universal Plug and Play (UPnP), remote management, or any exposed API endpoints. Alternatively, perform a network scan to identify unexpected listening ports.Affected if Remote management, UPnP, or other network services are enabled that could expose sensitive functions
A user is affected if they own a NETGEAR D3600 or D6000 router running firmware version before 1.0.0.76 and have remote management or sensitive services exposed to the network.
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.
From vendor data1.0.0.76
Update NETGEAR D3600 and D6000 devices to firmware version 1.0.0.76 or later to resolve the security misconfiguration.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21140 — 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-2018-21140 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