CVE-2020-8863
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 · uneditedThis vulnerability allows network-adjacent attackers to bypass authentication on affected installations of D-Link DIR-867, DIR-878, and DIR-882 routers with firmware 1.10B04. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of HNAP login requests. The issue results from the lack of proper implementation of the authentication algorithm. An attacker can leverage this vulnerability to escalate privileges and execute code in the context of the router. Was ZDI-CAN-9470.
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 confidenceThis is an authentication bypass vulnerability in D-Link DIR-867, DIR-878, and DIR-882 routers. The flaw exists in the HNAP (Home Network Administration Protocol) login request handling where the authentication algorithm is improperly implemented, allowing unauthenticated network-adjacent attackers to bypass authentication entirely and escalate privileges to execute code in the router context.
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.20b03<= 1.10b04<= 1.10b04CVSS 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 the router modelCheck the device label on the router or access the web interface and look for the model number (DIR-867, DIR-878, or DIR-882)Affected if The model is not one of DIR-867, DIR-878, or DIR-882, then this CVE does not apply
-
Determine the installed firmware versionAccess the router web interface, navigate to the Status or Management section, and locate the firmware version information. Alternatively, check the download file name if you have the firmware file.Affected if The firmware version cannot be determined or is higher than the affected ranges, then likely not vulnerable
-
Compare firmware version against affected rangesIf the model is DIR-878, check if version <= 1.20b03. For DIR-882, check if version <= 1.10b04. For DIR-867, check if version <= 1.10b04.Affected if The installed firmware version is at or below these thresholds, the device is potentially vulnerable
-
Verify HNAP interface accessibilityAttempt to access the router on the local network via HTTP/HTTPS to the HNAP endpoint (commonly at /HNAP1/ or similar). Check if the interface responds to HNAP requests.Affected if The HNAP interface is exposed and responds, the authentication bypass can be exploited by network-adjacent attackers
A user is affected if they have a DIR-867, DIR-878, or DIR-882 router running firmware at or below the specified version thresholds AND the HNAP interface is accessible on their network.
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 dataApply vendor firmware updates when available. Until patched, restrict network access to trusted users only since the attack vector requires network adjacency. If updates are unavailable, consider disabling HNAP functionality if exposed or replacing affected devices.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8863 — 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-2020-8863 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