dbcve.org
Dir 882 FirmwareOperating system · Dlink

CVE-2021-45998

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to after 1.30b06 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 device DIR_882 DIR_882_FW1.30B06_Hotfix_02 was discovered to contain a command injection vulnerability in the LocalIPAddress parameter. This vulnerability allows attackers to execute arbitrary commands via a crafted HNAP1 POST request.

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

A command injection vulnerability exists in D-Link DIR_882 routers running firmware DIR_882_FW1.30B06_Hotfix_02. The vulnerability is in the LocalIPAddress parameter and can be exploited through a crafted HNAP1 POST request, allowing authenticated attackers to execute arbitrary operating system commands on the affected device.

MitigationApply available vendor firmware patches; if no patch exists, network segment the device or replace with a supported model. Restrict HNAP service access to trusted networks or disable if unused.

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 882 FirmwareOperating system
Affected:<= 1.30b06= 1.30b06

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 device model
    Access the router web interface or check the device label to confirm the model is D-Link DIR-882
    Affected if The device is a D-Link DIR-882 router
  2. Check installed firmware version
    Log into the router web interface and navigate to Status or Management section to view the firmware version. Compare against affected versions 1.30b06 and earlier
    Affected if Firmware version is 1.30b06 or earlier, or specifically DIR_882_FW1.30B06_Hotfix_02
  3. Verify HNAP service status
    Check router configuration for HNAP (Home Network Administration Protocol) settings. This is typically found under Advanced or Management settings in the web interface
    Affected if HNAP service is enabled and accessible on the device
  4. Check remote management access
    Examine router firewall or access control settings to determine if HNAP or remote management is exposed to untrusted networks
    Affected if Remote management or HNAP is accessible from outside the local network or from untrusted hosts
  5. Confirm authentication is required for exploitation
    Review whether default credentials are in use or if attacker could obtain valid HNAP credentials through other means
    Affected if An attacker can obtain valid authentication credentials for the router's web interface

The device is affected if it is a D-Link DIR-882 running firmware version 1.30b06 or earlier with HNAP service enabled and accessible to the attacker.

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 1.30b06
Interim mitigation

Apply available vendor firmware patches; if no patch exists, network segment the device or replace with a supported model. Restrict HNAP service access to trusted networks or disable if unused.

Recommended fix Moderate confidence

Check D-Link official support channels for available firmware updates beyond version 1.30b06

  1. 1. Disable or block HNAP1 service at the network boundary/firewall if not required for normal operation
  2. 2. If HNAP is required, restrict access to trusted IP addresses only using the router's access control features
  3. 3. Monitor network traffic for suspicious HNAP1 POST requests with abnormal parameters
  4. 4. Consider placing the device behind an additional firewall or VLAN to limit exposure
  5. 5. Check D-Link support (supportannouncement.us.dlink.com) for available firmware updates that address this vulnerability

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

Fix this in Dir 882 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45998 — 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-2021-45998 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