CVE-2024-5293
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 · uneditedD-Link DIR-2640 HTTP Referer 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-2640-US routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within prog.cgi, 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 the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21853.
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 confidenceStack-based buffer overflow vulnerability in D-Link DIR-2640-US routers within prog.cgi when processing HNAP requests. The lack of proper length validation on user-supplied HTTP Referer header data allows an attacker to overflow a fixed-length stack buffer and execute arbitrary code in root context without authentication.
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= 1.11b02CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web administration interface and check the device information page, or log into the router via SSH if available and run 'cat /proc/dmu/model' or check the label on the deviceAffected if The device is not a D-Link DIR-2640-US unit, the check does not apply
-
Confirm the firmware versionIn the router's web interface, navigate to Status or Management section to view the firmware version, or check via CLI with 'cat /etc/version' if SSH is enabledAffected if The installed firmware version is not 1.11b02 (versions outside this specific release are not affected by this CVE)
-
Verify the HNAP endpoint is accessibleSend an HTTP request to the router's IP on port 80 or 443 targeting the prog.cgi endpoint with an HNAP action header, e.g., 'curl -I http://<router-ip>/prog.cgi' or check if the page respondsAffected if The router's web interface (prog.cgi) is not reachable from the network segment being checked
-
Check if remote management is exposedScan the router's public IP or interface IP for open ports 80 and 443 using 'nmap -p 80,443 <ip>' or verify firewall rules allow inbound HTTP/HTTPS trafficAffected if Ports 80 or 443 are accessible from untrusted networks (internet or guest segments), meaning the vulnerability is remotely exploitable
A user is affected if they operate a D-Link DIR-2640-US router on firmware version 1.11b02 with the web management interface (prog.cgi/HNAP) accessible from a network where an attacker could send malicious HTTP Referer headers.
Generated from the published advisory. Verify against your own configuration.
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 dataSince DIR-2640 is end-of-life with no official patch, restrict network access to the management interface (ports 80/443) via firewall rules or disable remote management; consider router replacement.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-5293 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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