CVE-2017-18846
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. This affects R6250 before 1.0.4.12, R6400v2 before 1.0.2.32, R7000P/R6900P before 1.0.0.56, R7900 before 1.0.1.18, R8300 before 1.0.2.100_1.0.82, R8500 before 1.0.2.100_1.0.82, and D8500 before 1.0.3.29.
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 firmware versions (R6250, R6400v2, R7000P/R6900P, R7900, R8300, R8500, D8500). The overflow occurs due to insufficient bounds checking in certain firmware components, potentially allowing authenticated attackers to execute arbitrary code or cause denial of service.
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.4.12< 1.0.2.32< 1.0.0.56< 1.0.0.56< 1.0.1.18< 1.0.2.100_1.0.82< 1.0.2.100_1.0.82< 1.0.3.29CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 router modelLocate the model number on the device label or log into the administrative web interface and check the status or device info pageAffected if Router model is R6250, R6400v2, R7000P, R6900P, R7900, R8300, R8500, or D8500
-
Check installed firmware versionLog into the router web interface, navigate to Administration > Firmware Update or Advanced > Administration > Router Status, and note the displayed firmware versionAffected if Firmware version is lower than the fixed version for your model (R6250 < 1.0.4.12, R6400 < 1.0.2.32, R7000P/R6900P < 1.0.0.56, R7900 < 1.0.1.18, R8300/R8500 < 1.0.2.100_1.0.82, D8500 < 1.0.3.29)
-
Verify remote administration accessCheck router settings under Advanced > Administration > Remote Management or similar, and determine if remote HTTP/HTTPS management is enabled and accessible from untrusted networksAffected if Remote management is enabled and accessible from external networks, increasing the attack surface for authenticated attackers
-
Review administrative account securityIn the router admin interface, verify that strong passwords are set for administrator accounts and that default credentials are not in useAffected if Weak or default administrative credentials are in use, allowing easier attainment of the authentication required for exploitation
You are affected if you own one of the listed router models and your firmware version is below the fixed version for that model, particularly if the administrative interface is accessible to untrusted users.
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.561.0.1.181.0.2.32
Apply vendor-supplied firmware updates: R6250 to 1.0.4.12+, R6400v2 to 1.0.2.32+, R7000P/R6900P to 1.0.0.56+, R7900 to 1.0.1.18+, R8300/R8500 to 1.0.2.100_1.0.82+, D8500 to 1.0.3.29+. If updates unavailable, restrict administrative interface access to trusted networks.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18846 — 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-18846 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