dbcve.org
Dir 822 FirmwareOperating system · Dlink

CVE-2018-20675

CRITICAL · 9.8 CVSS v3.1 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 3.10b06 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
D-Link DIR-822 C1 before v3.11B01Beta, DIR-822-US C1 before v3.11B01Beta, DIR-850L A* before v1.21B08Beta, DIR-850L B* before v2.22B03Beta, and DIR-880L A* before v1.20B02Beta devices allow authentication bypass.

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 DIR-822, DIR-850L, and DIR-880L router firmware versions before specified beta releases contain an authentication bypass vulnerability allowing unauthorized access to the device management interface without valid credentials. The CVSS 9.8 score indicates trivial exploitability and complete compromise potential.

MitigationUpdate affected router firmware to v3.11B01Beta (DIR-822), v1.21B08Beta (DIR-850L A*), v2.22B03Beta (DIR-850L B*), or v1.20B02Beta (DIR-880L A*) or later. If updates unavailable, restrict WAN access to management interfaces and monitor for unauthorized access.

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
Dir 822 FirmwareOperating system
Affected:<= 3.10b06
Dir 822 Us FirmwareOperating system
Affected:<= 3.10b06
Dir 850l FirmwareOperating system
Affected:<= 1.21b07<= 2.21b01= 2.22b02
Dir 880l FirmwareOperating system
Affected:<= 1.07.b08= 1.20b01

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify router model and firmware version
    Access the router web interface and navigate to Status or System Information page to view the hardware model and firmware version. Alternatively, check the label on the router device or the admin interface firmware upgrade page.
    Affected if The router is a DIR-822, DIR-850L, or DIR-880L model running firmware version 3.10b06 or lower for DIR-822, 1.21b07/2.21b01/2.22b02 for DIR-850L, or 1.07b08/1.20b01 for DIR-880L.
  2. Confirm firmware version is within affected range
    Compare the installed firmware version number to the affected ranges: DIR-822 and DIR-822 US <= 3.10b06; DIR-850L <= 1.21b07, <= 2.21b01, or = 2.22b02; DIR-880L <= 1.07b08 or = 1.20b01.
    Affected if The installed firmware version matches or is lower than any of the listed affected versions.
  3. Check if WAN management access is enabled
    In the router web interface, go to Setup or Advanced settings and look for Remote Management, WAN Access, or Web Management options. Verify if the management interface is accessible from the WAN (internet) side.
    Affected if Remote management or WAN access to the web interface is enabled, exposing the authentication bypass vulnerability to external attackers.
  4. Verify management interface accessibility
    Attempt to access the router login page from an external network using the public IP address, or check router firewall rules and port forwarding settings for port 80 or 443 forwarded to the router.
    Affected if The router management interface is reachable from the WAN without VPN or authentication bypass restrictions.

The environment is affected if the router is a DIR-822, DIR-850L, or DIR-880L model running one of the specified affected firmware versions and the management interface is exposed to WAN access.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.10b06
Interim mitigation

Update affected router firmware to v3.11B01Beta (DIR-822), v1.21B08Beta (DIR-850L A*), v2.22B03Beta (DIR-850L B*), or v1.20B02Beta (DIR-880L A*) or later. If updates unavailable, restrict WAN access to management interfaces and monitor for unauthorized access.

Recommended fix High confidence

v3.11B01Beta (DIR-822/DIR-822-US), v1.21B08Beta (DIR-850L A*), v2.22B03Beta (DIR-850L B*), or v1.20B02Beta (DIR-880L A*)

  1. 1. Identify the exact model number (e.g., DIR-822 C1, DIR-822-US C1, DIR-850L A*, DIR-850L B*, or DIR-880L A*) and current firmware version of your D-Link router
  2. 2. Access the router's web interface by entering its IP address in a web browser
  3. 3. Navigate to the Administration or Management section to view the current firmware version
  4. 4. Visit the official D-Link support website (support.dlink.com) and locate the firmware download page for your specific model
  5. 5. Download the appropriate fixed firmware version: v3.11B01Beta for DIR-822/DIR-822-US, v1.21B08Beta for DIR-850L A*, v2.22B03Beta for DIR-850L B*, or v1.20B02Beta for DIR-880L A*
  6. 6. In the router's web interface, go to the Firmware Upgrade or System section
  7. 7. Upload the downloaded firmware file and initiate the upgrade process
  8. 8. Wait for the upgrade to complete and the router to reboot automatically
Caveat Beta firmware releases may introduce stability or compatibility issues; ensure to review release notes if available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 822 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-20675 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