Skip to content
vulnerability

CVE-2024-0769

5.3
Medium
KEV · Exploited in wildEPSS 83%Patch available

** 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.

exploited
Yes, in CISA KEV since 25 Jun 2025fix by 16 Jul 2025 (CISA deadline for US federal agencies)
fix
Patch available see the advisory in the references
likelihood
EPSS 82.7%
Published 21 Jan 2024Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: yesAV · networkCWE-22· Path Traversal

Can a WAF block it? Yes. The attack is delivered via an HTTP POST request to /hedwig.cgi with a service parameter containing path traversal sequences (../), which are unusual and can be detected by a WAF rule matching such patterns. A WAF rule can match ../ sequences in the service parameter of /hedwig.cgi. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: ../ sequences in the service parameter of /hedwig.cgi

Also consider: patch · custom WAF rule · canonical path validation

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialitylowintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
common questions

Is CVE-2024-0769 being exploited?

Yes. CVE-2024-0769 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-0769?

CVE-2024-0769 is rated Medium with a CVSS score of 5.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-0769?

Yes. A fix has been recorded for CVE-2024-0769. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-0769 affect?

CVE-2024-0769 affects dlink:dir-859_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
dlink:dir-859_firmware
affected versions
D-Link DIR-859
  • affected1.06B01

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 26 Jun 2025 (SSVC 2.0.3).

timeline

  1. 21 Jan 2024Published
  2. 25 Jun 2025Added to CISA KEV (exploited in the wild) · 521 days (about 1 year) later
  3. 26 Jun 2025CISA SSVC assessment: exploitation active · 1 day later
  4. 16 Jul 2025CISA remediation due date (US federal agencies) · 20 days later
  5. 21 Oct 2025CVE record last updated · 98 days (about 3 months) later
  6. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
6 references in the CVE record: 1 exploit, 5 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved