CVE-2024-45694
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 · uneditedThe web service of certain models of D-Link wireless routers contains a Stack-based Buffer Overflow vulnerability, which allows unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.
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 confidenceA stack-based buffer overflow vulnerability exists in the web service component of multiple D-Link wireless router models. The vulnerability allows unauthenticated remote attackers to send specially crafted HTTP requests that overflow a stack buffer, enabling arbitrary code execution on the affected device.
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.01= 1.02= 1.04= 1.10= 1.00= 1.04CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your D-Link router modelCheck the device label or log into the web management interface to confirm the exact model number (Dir X5460 or Dir X4860)Affected if The model is Dir X5460 or Dir X4860 and matches affected hardware revisions
-
Check the installed firmware versionLog into the router web interface and navigate to Status or Management section to view the firmware version, or use the command line if availableAffected if The firmware version is 1.01, 1.02, 1.04, or 1.10 for Dir X5460; or 1.00 or 1.04 for Dir X4860
-
Verify if remote web management is enabledIn the router web interface, check under Advanced or Management settings for 'Remote Management' or 'Web Management' access settings to see if remote access is enabledAffected if Remote web management (HTTP/HTTPS access from WAN) is enabled on the device
-
Confirm web service is accessible from untrusted networksAttempt to access the router web interface from an external network or check router firewall rules to determine if the HTTP/HTTPS ports (80/443) are open to the WAN interfaceAffected if The router's web service is exposed directly to the internet or untrusted networks without VPN or firewall protection
You are affected if you have a Dir X5460 (versions 1.01, 1.02, 1.04, or 1.10) or Dir X4860 (versions 1.00 or 1.04) with remote web management enabled and the interface accessible from untrusted networks.
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 dataApply vendor-supplied firmware patches when available; if patches are unavailable, disable remote web management or place devices behind a VPN/firewall to restrict access to the management interface.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-45694 — 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-45694 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