dbcve.org
Dir 823 Pro FirmwareOperating system · Dlink

CVE-2021-46452

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to after 1.0.2 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 D-Link DIR-823-Pro v1.0.2 was discovered to contain a command injection vulnerability in the function SetNetworkTomographySettings. This vulnerability allows attackers to execute arbitrary commands via the tomography_ping_address, tomography_ping_number, tomography_ping_size, tomography_ping_timeout, and tomography_ping_ttl parameters.

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-823-Pro v1.0.2 routers in the SetNetworkTomographySettings function. Attackers can execute arbitrary OS commands by injecting shell metacharacters into ping-related parameters (tomography_ping_address, tomography_ping_number, tomography_ping_size, tomography_ping_timeout, tomography_ping_ttl), indicating a failure to sanitize user input before passing it to system shell commands.

MitigationApply vendor firmware patch if available; if end-of-life or no patch, disable the network tomography feature, implement network segmentation, and consider replacement of the affected 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
Dir 823 Pro FirmwareOperating system
Affected:<= 1.0.2

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 the device model
    Check the device label or web interface for the exact model number (DIR-823-Pro)
    Affected if Device is not a D-Link DIR-823-Pro router
  2. Check the firmware version
    Access the router web interface, navigate to Status or System settings, and locate the firmware version information
    Affected if Firmware version is 1.0.2 or lower
  3. Locate the Network Tomography settings
    In the router web interface, look for Network Tools, Network Diagnostics, or similar settings that contain Network Tomography or ping functionality
    Affected if The Network Tomography feature is present and accessible in the web interface
  4. Verify the vulnerable parameters exist
    Inspect the web form or HTTP requests for parameters named tomography_ping_address, tomography_ping_number, tomography_ping_size, tomography_ping_timeout, or tomography_ping_ttl
    Affected if Any of these five ping-related parameters are present in the interface

The device is affected if it is a D-Link DIR-823-Pro router running firmware version 1.0.2 or lower and the Network Tomography feature with these ping parameters is accessible.

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.0.2
Interim mitigation

Apply vendor firmware patch if available; if end-of-life or no patch, disable the network tomography feature, implement network segmentation, and consider replacement of the affected device.

Recommended fix Moderate confidence

DIR-823 Pro B1 firmware version 1.0.4 or later (latest available from D-Link support)

  1. 1. Visit the official D-Link support page at www.dlink.com and navigate to the DIR-823 Pro product support section.
  2. 2. Locate and download the latest firmware version available for the DIR-823 Pro hardware revision B1.
  3. 3. Access the router's web administration interface by entering the default IP address (typically 192.168.0.1) in a web browser.
  4. 4. Log in with the administrator credentials (default credentials are usually admin/admin, but check the device label or manual).
  5. 5. Navigate to the 'System' or 'Management' settings section and locate the 'Firmware Upgrade' or 'Router Upgrade' option.
  6. 6. Click 'Browse' or 'Choose File' and select the downloaded firmware file.
  7. 7. Click 'Upload' or 'Upgrade' to begin the firmware update process.
  8. 8. Wait for the upload to complete and the router to reboot automatically (do not power off the device during this process).
Caveat Firmware updates may reset router configuration to defaults; backup current settings before upgrading if possible

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

Fix this in Dir 823 Pro Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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