dbcve.org
Dir X3260 FirmwareOperating system · Dlink

CVE-2023-51619

MEDIUM · 6.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.04b01 or later.
See remediation →
70/100
Remediation priority · Elevated
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 DIR-X3260 prog.cgi SetMyDLinkRegistration Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DIR-X3260 routers. Authentication is required to exploit this vulnerability. The specific flaw exists within the prog.cgi binary, which handles HNAP requests made to the lighttpd webserver listening on TCP ports 80 and 443. The issue results from the lack of proper validation of a user-supplied string before copying it to a fixed-size stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21667.

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

Stack-based buffer overflow in the prog.cgi binary of D-Link DIR-X3260 routers. The vulnerability stems from improper validation of user-supplied strings in HNAP requests before copying them to a fixed-size stack buffer, allowing authenticated attackers to achieve RCE as root.

MitigationCheck vendor for available firmware updates; if unavailable, replace the end-of-life device and implement network segmentation to limit exposure to trusted users only.

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 X3260 FirmwareOperating system
Affected:< 1.04b01

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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 device model
    Access the router admin interface or check the device label/marketing to confirm the model is D-Link DIR-X3260
    Affected if The device is a D-Link DIR-X3260 router
  2. Check firmware version
    Log into the router web interface (usually at 192.168.0.1) and navigate to Status or Management section to view the firmware version, or use the command line and check /etc/version or the output of 'cat /proc/version' if SSH/telnet is available
    Affected if The firmware version is anything less than 1.04b01 (e.g., 1.03, 1.02, etc.)
  3. Verify HNAP service accessibility
    Attempt to access the HNAP endpoint by sending an HTTP request to the router (e.g., curl http://192.168.0.1/HNAP1/ or check if port 80/443 responds to HNAP SOAP requests)
    Affected if HNAP interface is exposed and accepts requests without additional network segmentation
  4. Confirm prog.cgi binary presence
    If command-line access is available (via SSH/telnet), check for the existence of prog.cgi in the web server's cgi-bin directory, typically at /www/cgi-bin/prog.cgi or similar path
    Affected if The prog.cgi binary exists and is executable on the device

You are affected if you have a D-Link DIR-X3260 router running firmware version lower than 1.04b01 with the HNAP interface accessible to untrusted users.

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 1.04b01 or later
Fixed in 1.04b01
Interim mitigation

Check vendor for available firmware updates; if unavailable, replace the end-of-life device and implement network segmentation to limit exposure to trusted users only.

Recommended fix High confidence

D-Link DIR-X3260 Firmware version 1.04b01 or later

  1. 1. Download the firmware version 1.04b01 or later from the official D-Link support website for the DIR-X3260 router.
  2. 2. Access the router's web administration interface by navigating to the device's IP address (typically 192.168.0.1).
  3. 3. Log in with administrator credentials.
  4. 4. Navigate to the firmware update section (usually under 'Management' or 'Settings').
  5. 5. Upload the downloaded firmware file and initiate the upgrade process.
  6. 6. Wait for the firmware to upload and install - do not power off the router during this process.
  7. 7. After the router reboots, verify the firmware version has been updated to 1.04b01 or later.
  8. 8. Confirm the router is functioning normally and all services are operational.
Caveat Standard firmware upgrade - ensure backup of configuration; router will briefly be unavailable during the update process

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

Fix this in Dir X3260 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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