Dva 2800 FirmwareOperating system · Dlink

CVE-2020-27863

MEDIUM · 6.5 CVSS v3.1 Published 2021-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of D-Link DVA-2800 and DSL-2888A routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the dhttpd service, which listens on TCP port 8008 by default. The issue results from incorrect string matching logic when accessing protected pages. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-10912.

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 confidence

D-Link DVA-2800 and DSL-2888A routers contain a path traversal or improper access control vulnerability in the dhttpd web service (TCP port 8008). The flaw stems from incorrect string matching logic when the router processes requests for protected pages, allowing unauthenticated attackers to bypass authentication and retrieve stored credentials from the device configuration.

MitigationApply the latest firmware update from D-Link for the affected router models. If no update is available, restrict network access to TCP port 8008 via firewall rules to prevent external attackers from reaching the vulnerable service, and immediately rotate any credentials that may have been stored on 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
Dva 2800 FirmwareOperating system
Affected:= 2.30_au
Dsl 2888a FirmwareOperating system
Affected:= 2.30_au

CVSS 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
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the router web interface and check the device info page, or SSH into the router and run 'cat /proc/cpuinfo' or check the model via 'nvram get model'
    Affected if The device model is D-Link DVA-2800 or DSL-2888A
  2. Check firmware version
    Access router web interface under Status or Administration section, or SSH in and run 'nvram get firmware_version' or 'cat /etc/version'
    Affected if The firmware version is exactly 2.30_au
  3. Verify dhttpd service is exposed
    From an external or internal host, run 'nc -zv <router_ip> 8008' or use nmap: 'nmap -p 8008 <router_ip>' to check if TCP port 8008 is open and listening
    Affected if Port 8008 is open and responding on the target router
  4. Check for authentication bypass vulnerability
    Send a crafted HTTP request to port 8008 attempting to access a protected configuration page without credentials. Common paths to test include '/admin/backupsettings.conf' or similar configuration export endpoints based on the dhttpd path traversal issue
    Affected if The router responds with sensitive configuration data or credentials without requiring authentication on port 8008

The environment is affected if the device is a D-Link DVA-2800 or DSL-2888A running firmware version 2.30_au with the dhttpd service (port 8008) exposed and responding, allowing unauthenticated access to sensitive configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest firmware update from D-Link for the affected router models. If no update is available, restrict network access to TCP port 8008 via firewall rules to prevent external attackers from reaching the vulnerable service, and immediately rotate any credentials that may have been stored on the device.

Fix this in Dva 2800 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27863 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-27863 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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