dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-45623

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-02
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 DAP-2310 Hardware A Firmware 1.16RC028 allows remote attackers to execute arbitrary code via a stack-based buffer overflow in the ATP binary that handles PHP HTTP GET requests for the Apache HTTP Server (httpd). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

D-Link DAP-2310 access point firmware 1.16RC028 contains a stack-based buffer overflow vulnerability in the ATP binary that processes PHP HTTP GET requests destined for the Apache HTTP Server (httpd). Attackers can send specially crafted HTTP GET requests to trigger the overflow and achieve remote arbitrary code execution on the affected device.

MitigationSince this product is end-of-life and no longer receives firmware updates, immediate mitigation requires network isolation (placing the device behind a firewall with restrictive ACLs), disabling the device if possible, or replacing with a supported alternative. If the device must remain in service, restrict external access to the HTTP service and monitor for exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 device model
    Access the device web interface or check the device label/metadata to confirm the model is D-Link DAP-2310
    Affected if Device is a D-Link DAP-2310 and the firmware version is 1.16RC028 or earlier (the only version mentioned as affected)
  2. Check firmware version
    Log into the device admin interface and navigate to the status or system information page to view the installed firmware version. Compare against 1.16RC028.
    Affected if Firmware version is 1.16RC028 (the only confirmed affected version)
  3. Verify HTTP service is enabled
    Attempt to access the device's web interface via HTTP on the standard ports (typically 80/tcp). The vulnerability requires the Apache HTTP Server (httpd) to be processing requests.
    Affected if HTTP service is exposed and accessible on the device
  4. Confirm ATP binary presence
    If you have SSH/telnet access to the device, check for the presence of the ATP binary in the filesystem, typically found in /htdocs/web/ or similar paths where CGI binaries reside
    Affected if ATP binary exists and is being used to process PHP HTTP requests

The device is affected if it is a D-Link DAP-2310 running firmware version 1.16RC028 with the HTTP service enabled and the ATP binary present, as the vulnerability requires all these conditions to be exploitable via crafted HTTP GET 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since this product is end-of-life and no longer receives firmware updates, immediate mitigation requires network isolation (placing the device behind a firewall with restrictive ACLs), disabling the device if possible, or replacing with a supported alternative. If the device must remain in service, restrict external access to the HTTP service and monitor for exploitation attempts.

Recommended fix High confidence
  1. This vulnerability affects D-Link DAP-2310 Hardware A Firmware 1.16RC028, which is an end-of-life product no longer supported by the vendor.
  2. No vendor patch, firmware update, or configuration mitigation is available for this vulnerability.
  3. Replace the affected D-Link DAP-2310 device with a currently supported model from D-Link or another vendor.
  4. If replacement is not immediately possible, isolate the device behind a firewall with strict access controls to limit exposure to unauthenticated attackers.
Caveat Product is end-of-life with no vendor support; no upgrade available

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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