CVE-2017-10854
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 · uneditedCorega CG-WGR1200 firmware 2.20 and earlier allows an attacker to bypass authentication and change the login password 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 confidenceThe Corega CG-WGR1200 wireless router firmware versions 2.20 and earlier contains an authentication bypass vulnerability in its web management interface. Attackers can exploit unspecified vectors to bypass the login authentication mechanism and subsequently change the administrator password, gaining full control of the device.
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 modelLocate the physical router or access its web management interface and confirm the model number is Corega CG-WGR1200. This is typically displayed on a status page or in the device header.Affected if The device model is Corega CG-WGR1200 and the firmware version is 2.20 or lower.
-
Determine the installed firmware versionAccess the router web management interface and navigate to the firmware or system information page. Look for a version field that displays the firmware revision number. If telnet or SSH access is available, use it to retrieve the firmware version from the system settings.Affected if The displayed firmware version is 2.20 or any version number lower than 2.20.
-
Verify the web management interface is enabledCheck the router administrative settings to confirm the HTTP/HTTPS web management interface is turned on. This is usually found under Administration, Management, or Access settings.Affected if The web management interface is enabled and accessible from the network segment being assessed.
-
Confirm administrative access controlsAttempt to access the router login page from the network perspective you are evaluating. Note whether authentication is required or if the interface is exposed without restrictions.Affected if The login page is directly accessible and the authentication mechanism may be bypassed based on the affected version range.
If the device is a Corega CG-WGR1200 running firmware version 2.20 or lower with the web management interface enabled and accessible, the environment is affected by this authentication bypass 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 dataUpdate the router firmware to a version newer than 2.20. If updating is not immediately possible, restrict administrative access to trusted networks only and monitor for unauthorized configuration changes.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10854 — 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-10854 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