Dir 878 FirmwareOperating system · Dlink

CVE-2023-24798

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_475FB0 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 overflow vulnerability exists in the sub_475FB0 function of D-Link DIR878 router firmware DIR_878_FW120B05. Attackers can exploit this by sending a crafted payload, potentially achieving arbitrary code execution or causing a complete denial of service.

MitigationApply available firmware updates from D-Link; if no patch exists, implement network segmentation and restrict access to the device's management interface.

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. Check installed firmware version
    Access the router's web administration interface (typically at 192.168.0.1) and navigate to Status or Management section to view the firmware version. Alternatively, use the command line and check via 'cat /proc/version' or 'nvram get firmware_version' if telnet/ssh is enabled.
    Affected if The displayed firmware version is exactly 1.20b05 (DIR_878_FW120B05)
  2. Verify router model
    Confirm the device is specifically a D-Link DIR-878 model by checking the device label or the web interface status page.
    Affected if The model is D-Link DIR-878 and firmware matches version 1.20b05
  3. Check if remote management is enabled
    Log into the router web interface and examine the Administration or Management settings to determine if remote management (HTTP/HTTPS from WAN) is enabled.
    Affected if Remote management or WAN access to the router's web interface is enabled, providing an attack vector to the vulnerable function
  4. Identify exposed services
    From an external network perspective, scan the router's public IP for open HTTP/HTTPS ports (typically ports 80, 443, 8080, 8443) using nmap or similar tool: 'nmap -p 80,443 <router-public-ip>'.
    Affected if The router's web management interface is exposed on WAN IP addresses, allowing external attackers to send crafted payloads to the sub_475FB0 function
  5. Confirm vulnerable function presence
    Since this is a firmware-level vulnerability in function sub_475FB0, there is no direct runtime check. The vulnerability exists if firmware version 1.20b05 is running.
    Affected if Firmware version 1.20b05 is confirmed to be running on the DIR-878 device

The environment is affected if the D-Link DIR-878 router is running firmware version 1.20b05 and has its management interface accessible to untrusted networks.

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 available firmware updates from D-Link; if no patch exists, implement network segmentation and restrict access to the device's management interface.

Fix this in Dir 878 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-24798 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