CVE-2017-10814
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 · uneditedBuffer overflow in CG-WLR300NM Firmware version 1.90 and earlier allows an attacker to execute arbitrary code via unspecified vectors.
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 confidenceBuffer overflow vulnerability in CG-WLR300NM router firmware versions 1.90 and earlier allows an attacker to execute arbitrary code via unspecified vectors. The vulnerability has a CVSS score of 6.8 (MEDIUM), indicating moderate exploitability with impact primarily on confidentiality and integrity.
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.90CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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.
-
Confirm device model is Corega WLR300NMAccess the router's web administration interface (typically at 192.168.1.1) and navigate to the status or device information page to verify the model name displays as 'WLR300NM' or 'WLR-300NM'. Alternatively, check the physical device label on the router chassis.Affected if The device is a Corega WLR300NM router
-
Retrieve the installed firmware versionLog into the router's web interface and locate the firmware version in the system status, maintenance, or firmware upgrade section. If CLI access is available, use the router's command interface (telnet or SSH) to run the appropriate version display command.Affected if The firmware version cannot be verified or the device is inaccessible for version checking
-
Compare installed version against affected rangeNote the exact firmware version string displayed (for example, 1.90, 1.80, 1.70) and determine whether it is less than or equal to 1.90. The affected range includes versions 1.90 and all prior releases.Affected if The installed firmware version is 1.90 or lower (1.90, 1.80, 1.70, etc.)
-
Verify if administrative interfaces are network-accessibleCheck router configuration for exposed management services such as HTTP/HTTPS web interface, telnet, or SSH that are listening on WAN or unrestricted LAN interfaces. Review firewall or access control settings.Affected if Remote administrative access is enabled and the device is network-accessible beyond trusted segments
A user is affected if they are running Corega WLR300NM firmware version 1.90 or lower, as this version range contains the buffer overflow 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.
From vendor dataIf vendor-supplied patched firmware is available, update to the latest version. If no patch is available, consider replacing the device with a currently supported model. If the device must remain in service, implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10814 — 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-10814 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