dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 Jul 2025.
Dir 859 FirmwareOperating system · Dlink

CVE-2024-0769

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DIR-859 1.06B01. It has been rated as critical. Affected by this issue is some unknown functionality of the file /hedwig.cgi of the component HTTP POST Request Handler. The manipulation of the argument service with the input ../../../../htdocs/webinc/getcfg/DHCPS6.BRIDGE-1.xml leads to path traversal. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-251666 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.

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 path traversal vulnerability in D-Link DIR-859 firmware 1.06B01 allows remote attackers to read arbitrary files via the hedwig.cgi component by manipulating the service parameter with traversal sequences (../../../../) to access sensitive configuration files like DHCPS6.BRIDGE-1.xml. The vulnerability has a CVSS 9.8 critical rating and publicly available exploits.

MitigationSince D-Link DIR-859 is end-of-life and unsupported, replace the device with a currently supported model. As an interim compensating control, restrict network access to the device's management interface using firewall rules or network segmentation.

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 859 FirmwareOperating system
Affected:= 1.06

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. Confirm device model
    Access the router web interface or check the device label to verify the model is D-Link DIR-859
    Affected if The device is not a D-Link DIR-859 router
  2. Check firmware version
    Log into the router web interface and navigate to the Status or Management page to view the firmware version, or use the router's administrative CLI if available
    Affected if The firmware version is 1.06 (specifically 1.06B01)
  3. Verify hedwig.cgi accessibility
    Attempt to access the URI /hedwig.cgi on the router's IP address using a web browser or curl command
    Affected if The hedwig.cgi endpoint responds (indicating the web interface is active)
  4. Check remote management exposure
    Review the router's web management settings to determine if remote access/management is enabled from WAN interfaces
    Affected if Remote management from WAN is enabled and the router is accessible from the internet

The environment is affected if the device is a D-Link DIR-859 running firmware version 1.06 with the hedwig.cgi web interface accessible, particularly if remote management is enabled.

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

Since D-Link DIR-859 is end-of-life and unsupported, replace the device with a currently supported model. As an interim compensating control, restrict network access to the device's management interface using firewall rules or network segmentation.

Recommended fix High confidence
  1. Replace the D-Link DIR-859 device with a currently supported model from D-Link or another vendor, as this product has reached end-of-life and no longer receives security updates from the manufacturer.
  2. If immediate replacement is not possible, isolate the device behind a firewall with strict ingress/egress filtering to limit exposure to the path traversal vulnerability.
  3. Disable remote management interfaces if not required, and restrict access to trusted IP addresses only.

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

Fix this in Dir 859 Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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