CVE-2020-27865
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 execute arbitrary code on affected installations of D-Link DAP-1860 firmware version 1.04B03 WiFi extenders. Authentication is not required to exploit this vulnerability. The specific flaw exists within the uhttpd service, which listens on TCP port 80 by default. The issue results from incorrect string matching logic when accessing protected pages. An attacker can leverage this vulnerability to escalate privileges and execute code in the context of the device. Was ZDI-CAN-10894.
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 confidenceA path traversal or authentication bypass vulnerability exists in the uhttpd web server service on D-Link DAP-1860 WiFi extenders (firmware 1.04B03). The service incorrectly validates string matching when handling requests to protected pages, allowing unauthenticated network-adjacent attackers to access privileged functionality and execute arbitrary code in the device 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.04b03CVSS 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.
-
Confirm device model is D-Link DAP-1860Access the device web management interface and check the status page or system information section, or log into the device CLI and run 'cat /proc/sys/kernel/random/uuid' or check the label on the device for the model number.Affected if The device is not a D-Link DAP-1860 model.
-
Check installed firmware versionIn the web interface, navigate to System > Firmware Upgrade or Status page to view the current firmware version. For CLI access, run 'cat /proc/version' or 'nvram get firmware_version' if available.Affected if The firmware version is 1.04B03 or any version prior to it (lower version numbers).
-
Verify uhttpd web server is runningCheck if the uhttpd process is active by running 'ps | grep uhttpd' via CLI or by inspecting the running processes in the device admin panel.Affected if The uhttpd service is not running on the device.
-
Check management interface network exposureReview network firewall rules or ACLs on your router/gateway to determine if the DAP-1860 management port (typically HTTP port 80/HTTPS port 443) is accessible from untrusted network segments or the internet.Affected if The device management interface is accessible from networks outside your trusted local network (e.g., WAN/internet-facing or from guest WiFi segments).
-
Test for authentication bypass vulnerabilityFrom a non-authenticated state, attempt to access a protected page directly by browsing to specific paths like /admin/ or /cgi-bin/ without providing credentials. If the page loads without redirecting to a login prompt, the device may be vulnerable.Affected if Protected administrative pages load without requiring authentication.
The device is affected if it is a D-Link DAP-1860 with firmware version 1.04B03 or earlier, the uhttpd web server is active, and the management interface is accessible to untrusted network attackers who could exploit the authentication bypass.
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-supplied firmware patches when available; until then, restrict network access to the device's management interface using firewall rules or network segmentation to limit exposure to only trusted local network segments.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27865 — 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-27865 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