CVE-2017-18738
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 a stack-based buffer overflow by an unauthenticated attacker. This affects EX6150v2 before 1.0.1.54, R6400 before 1.0.1.24, R6400v2 before 1.0.2.32, R6700 before 1.0.1.22, R6900 before 1.0.1.22, R7000 before 1.0.9.10, R7000P before 1.2.0.22, R6900P before 1.2.0.22, R7100LG before 1.0.0.32, R7300DST before 1.0.0.54, R7900 before 1.0.1.18, R8000 before 1.0.3.48, R8300 before 1.0.2.106, R8500 before 1.0.2.106, R6100 before 1.0.1.16, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, and WNR2000v5 before 1.0.0.58.
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 confidenceStack-based buffer overflow vulnerability in multiple NETGEAR router models (EX6150v2, R6400, R6700, R7000, R8000, R8300, R8500, and others) allows unauthenticated remote attackers to potentially execute arbitrary code or cause denial of service by overflowing a stack-based buffer.
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.1.54< 1.0.1.24< 1.0.2.32< 1.0.1.22< 1.0.1.22< 1.0.9.10< 1.2.0.22< 1.2.0.22< 1.0.0.32CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your NETGEAR router modelLocate the model number on the device label (usually on the bottom or back of the router) or log into the router web interface and check the firmware/update page for the model name. Confirm it is one of the affected models: EX6150v2, R6400, R6700, R6900, R7000, R7000p, R6900p, R8000, R8300, R8500, or R7100lg.Affected if The router model matches one of the listed affected models
-
Check firmware version via web interfaceLog into the router web interface (typically at 192.168.1.1 or 192.168.0.1). Navigate to Administration > Firmware Update or Advanced > Administration > Router Update. Record the displayed firmware version number.Affected if The displayed firmware version is lower than the patched version for your model (see version ranges: Ex6150 < 1.0.1.54, R6400 < 1.0.1.24 or < 1.0.2.32, R6700 < 1.0.1.22, R6900 < 1.0.1.22, R7000 < 1.0.9.10, R7000p < 1.2.0.22, R6900p < 1.2.0.22, R7100lg < 1.0.0.32)
-
Check firmware version via command lineIf telnet or SSH access is enabled on the router, connect and run the command 'version' or 'nvram get firmware_version' to retrieve the firmware version.Affected if The command output shows a version number lower than the patched version for your specific model
-
Verify the vulnerability trigger conditionThis is a stack-based buffer overflow in the router firmware that can be triggered by sending specially crafted network requests to the device. The flaw is exploitable without authentication.Affected if The router is exposed to untrusted network traffic (such as directly on the internet or an untrusted network segment) and runs a vulnerable firmware version
You are affected if your NETGEAR router model matches one of the listed models AND your current firmware version is below the patched version number for that model.
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.321.0.1.221.0.1.24
Update affected NETGEAR router firmware to the patched versions specified in the advisory (e.g., R7000 to 1.0.9.10, R8000 to 1.0.3.48). If firmware updates are unavailable, consider network segmentation or device replacement.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18738 — 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-18738 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