dbcve.org
Dir 878 FirmwareOperating system · Dlink

CVE-2023-24799

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-07
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
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 DIR878 DIR_878_FW120B05 was discovered to contain a stack overflow in the sub_48AF78 function. This vulnerability allows attackers to cause a Denial of Service (DoS) or execute arbitrary code via a crafted payload.

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 · moderate confidence

A stack buffer overflow vulnerability exists in the sub_48AF78 function of D-Link DIR878 firmware DIR_878_FW120B05. Attackers can send a crafted payload to trigger the overflow, potentially achieving remote code execution or causing device denial of service. The critical CVSS score of 9.8 indicates unauthenticated, network-adjacent exploitation is possible.

MitigationApply the vendor-supplied firmware patch when available. Until then, restrict network exposure of the device and monitor for suspicious traffic patterns targeting the affected function.

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 878 FirmwareOperating system
Affected:= 1.20b05

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
    Access the router web interface (typically http://192.168.0.1) or check the device label, then navigate to Status or System Information page to confirm the exact model is D-Link DIR 878
    Affected if Device model is not D-Link DIR 878, then not affected by this specific CVE
  2. Check the installed firmware version
    In the router web interface, go to Tools > System > Firmware Upgrade or Status page and locate the firmware version field. Alternatively, check via command line if SSH/Telnet is enabled: cat /etc/version or cat /proc/version
    Affected if Firmware version is exactly 1.20b05 (the only affected version listed)
  3. Determine if remote management is enabled
    In the router web interface, go to Tools > Administration or Management settings and check if Remote Management (WAN access) is enabled. Note the IP address or range allowed if configured
    Affected if Remote management is exposed to untrusted networks (WAN), increasing exposure
  4. Check for the vulnerable service availability
    Attempt to access the router's HTTP/HTTPS service from the WAN IP using a web browser. The vulnerable function sub_48AF78 is triggered via specific HTTP requests to the web server
    Affected if The router web interface is accessible from WAN (internet), making the vulnerability exploitable over the network
  5. Review router logs for suspicious requests
    In the router web interface, go to Status > Logs or Tools > System Log to examine recent access logs. Look for unusual HTTP requests, especially to unusual endpoints or with abnormal parameter lengths
    Affected if Logs show unexpected or malformed HTTP requests targeting the web interface, potentially indicating exploitation attempts

The environment is affected only if the device is a D-Link DIR 878 running firmware version 1.20b05 and the router management interface is exposed to the network where attackers can send crafted requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware patch when available. Until then, restrict network exposure of the device and monitor for suspicious traffic patterns targeting the affected function.

Fix this in Dir 878 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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