CVE-2017-10852
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 Corega CG-WGR1200 firmware 2.20 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 Corega CG-WGR1200 wireless router firmware version 2.20 and earlier allows attackers to execute arbitrary code, likely by overflowing a buffer in an unspecified network-facing service or input handling routine.
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<= 2.20CVSS 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.0/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 the router modelCheck the device label or web interface to confirm it is a Corega CG-WGR1200 wireless router. The model number is typically printed on a sticker on the device bottom or accessible via the admin web interface at the default gateway.Affected if The device is not a Corega CG-WGR1200, then this specific CVE does not apply.
-
Check the installed firmware versionLog into the router admin web interface and navigate to the firmware or system information page. The version is usually displayed as 'Firmware Version' or 'Software Version'. Alternatively, check the firmware file name if you have manually updated the router.Affected if The firmware version is 2.20 or lower, the device is within the affected version range.
-
Verify network-facing services are accessibleCheck the router administration settings to see if remote management or administration from the WAN (internet) side is enabled. Look for settings labeled 'Remote Management', 'Remote Access', 'Allow access from WAN', or similar. Also identify any exposed network services by scanning the router's WAN IP for open ports.Affected if Remote management is enabled or other network-facing services are exposed to untrusted networks, the vulnerability is potentially exploitable from outside the local network.
-
Assess network exposureDetermine if the router WAN interface is directly reachable from the internet (public IP address, not behind carrier-grade NAT). Check if the router has any port forwards or firewall rules that expose internal services. Use an external port scanner or check router logs for connection attempts.Affected if The router is directly internet-facing with network services exposed, an attacker could potentially trigger the buffer overflow remotely.
The device is affected if it is a Corega CG-WGR1200 router running firmware version 2.20 or lower AND has network-facing services or remote administration accessible from untrusted networks.
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 dataUpdate router firmware to a patched version if available; if no update exists, consider network segmentation or replacing the device, as arbitrary code execution on a network edge device poses significant risk.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10852 — 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-10852 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