CVE-2018-20674
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 · uneditedD-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 authenticated remote command execution.
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 confidenceMultiple D-Link router models (DIR-822 C1, DIR-822-US C1, DIR-850L A/B, DIR-880L A) contain an authenticated remote command execution vulnerability in firmware versions prior to the specified beta releases. Attackers with valid administrative credentials can execute arbitrary commands on affected devices via the web interface.
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<= 3.10b06<= 3.10b06<= 1.21b07<= 2.21b01= 2.22b02<= 1.07.b08= 1.20b01CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 modelAccess the device's web administrative interface and navigate to Status or System Information page to confirm the exact model (DIR-822 C1, DIR-822-US C1, DIR-850L A/B, or DIR-880L A)Affected if Model is not one of the affected D-Link models listed in the CVE
-
Determine the firmware versionIn the device web interface, go to Status or System Settings and locate the firmware version field. Compare the version number to the affected ranges: DIR-822 <= 3.10b06, DIR-850L <= 1.21b07 OR <= 2.21b01 OR = 2.22b02, DIR-880L <= 1.07b08 OR = 1.20b01Affected if Firmware version falls within any of the affected version ranges for the identified model
-
Verify web interface accessibilityCheck if the device administrative web interface (HTTP/HTTPS on ports 80 or 443) is reachable from network segments that are not trusted or are exposed to the internetAffected if The administrative web interface is accessible from untrusted networks (the vulnerability requires web interface access to be exploitable)
A user is affected if they have a DIR-822, DIR-850L, or DIR-880L device running firmware version within the specified affected ranges AND the device administrative web interface is network-accessible to potential attackers.
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 affected devices to firmware version v3.11B01Beta or later for DIR-822, v1.21B08Beta or later for DIR-850L A*, v2.22B03Beta or later for DIR-850L B*, and v1.20B02Beta or later for DIR-880L A*. Until patched, restrict administrative web interface access to trusted IP addresses and ensure strong, unique credentials.
- 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-2018-20674 — 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-2018-20674 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